Re: [Plone-developers] jenkins and git repository monitoring

Hi Laurence,

Am 06.02.2012 15:02, schrieb Laurence Rowe:
> We really should be running all tests across all packages following a
> push to any package. For example, it's possible that a change to
> plone.app.layout might cause a failure in a Products.CMFPlone test and
> we want to catch that as early as possible. The key advantage of
> Continuous Integration is that these failures are caught, everyone
> should already be running the tests on the package they're making
> changes too locally before committing. CI lets us catch those knock-on
> failures that might not otherwise be noticed.

I agree. Running all tests across all packages on any commit would be
desirable for exactly the reasons you pointed out. The more I think
about it, the more important it seems to me that we really run all tests
on each commit. CI only works if regressions are catched right away.

The reason why we thought about splitting up the build and running tests
on the packages itself (and run the full tests on an hourly basis), was
that we ran into performance issues with our two CI servers.

To solve this, we can either throw more hardware at our CI setup or find
a smart way to decide on which commits we have to trigger which jobs, to
reduce the number of jobs that Jenkins has to run. Right now we have to
run all three Plone coredev jobs with all tests for every commit on any
github/svn package that is in one of these buildouts. This seems to be
too much for our current setup and we want to run code analysis and
other coredev and add-on product jobs in the future as well.

Cheers,
timo

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Plone-website mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-website
The Wiki: http://plone.org/development/current/projects/WebsiteTeam