On Mon, Oct 17, 2011 at 9:02 PM, David Gerard <[email protected]> wrote: > On 17 October 2011 21:58, Chad <[email protected]> wrote: >> On Mon, Oct 17, 2011 at 8:54 PM, Platonides <[email protected]> wrote: > >>> How does it work? What is it good for? >>> Can we eg. add a task to jenkins which runs php -l on all files? > >> It works like CruiseControl did (only nicer). It runs any sort of >> automated build/testing processes we can script up (using Ant). > > > I'm curious - we run CC at work (and it's fine). Why Jenkins rather > than CC (or any other CI tool)? >
We ran CC for awhile. During the process of building this into a permanent service rather than an ad-hoc VM, I played with Jenkins and found it to be a very good replacement. Couple of reasons: * It has a large plugin community, and has ready support for PHPunit, SVN and Git. There are also plugins for Bugzilla and Gerrit tie-ins. * It has LDAP integration out of the box -- this was a big selling point * The UI is much cleaner and easier to use * Full log output from each run is available via the UI, making it easier to diagnose problems (rather than having to track down a shell user to pull the server logs) * The logo is a butler I could go on :) -Chad _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
