On 1/11/13 20:09 , Rom Walton wrote: >> let a continuous integration system (like Jenkins) do the testing for > you. > > I'm kind of partial to Trac's Bitten myself. > > http://bitten.edgewall.org/build/trunk
Sure, whatever tool does the job for you. Proper process integration in the daily workflow is more important to me than the actual tool used. Of course a CI tool shouldn't get in your way by any means, so you want to make sure it fulfills your requirements. FWIW, we focused on: > * Open source software (non-proprietary software) > * Ability to support language-agnostic, shell script style builds > * Ability to support master/slave (distributed) builds for various platforms > * Full Git support > * Considerable community/industry adoption and active project maintenance > * Asset: customizable builds (pre/post actions, like app-dir contraction and > artifact renaming) > * Asset: deployment support (add new builds to our test project automatically) > * Asset: easy build job maintenance and useful status visualization Based on this our short list comprised CruiseControl, buildbot and Jenkins. Evaluation summary: while buildbot seemed highly flexible and configurable it also seemed cumbersome to use. Jenkins offered the best compromise and can also be considered industry standard. Thus we tried Jenkins first. In the event that it wouldn't have worked out for us we'd given buildbot a try. CruiseControl's support for distributed builds was just not up to par with the other two, so we didn't evaluate it further. Based on this we took Jenkins for a test drive. It fulfilled all our expectations so far and we use it in production mode. The current system is integrated with our Gitorious git hosting system, triggering CI builds on each SCM push for selected projects. Notifications are being sent based on the given build job and its status transitions. We also plan to set up automatic deployment of successful builds on our test project. Right now we use one master and 13 slaves (various Linux and OS X slaves, physical boxes as well as VMs) to build our four main science and graphics apps, producing a total of about 25 binary versions. This was just meant to give you an idea and to share our experiences. If you have further questions, let me know. If you feel comfortable with Bitten, give it a try. Cheers, Oliver _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
