For a more recent list of CI requirements and analysis, see the Continuous Build page.

We've been using Jenkins as our CI tool for a long time now. However we've had a lot of stability issues (slow UI mostly) and as a result we've tried to look for an alternative.

Here are the important use cases that we wish to cover with our CI software:

Use CasesJenkinsTeamCity
Be able to have a display for running our Selenium testsaccept XVNC pluginaccept Command line steps to start/stop VNC using a shell script
Easily add new jobs when a new branch is created (when RC is released for example)accept Scriptler plugin with Groovy scripthelp
Easily remove all jobs for a given branch (for cleanup)accept Scriptler plugin with Groovy scripthelp
Don't send emails on false positivesaccept Scriptler + Mail Ext + PostBuild pluginshelp Might be possible using Build Failure Conditions: uncheck "the build process exit code is not zero" and then use "Fail build on specific text in build log" but it's probably difficult to use since we need to say "do not fail the build if this appears in the log" and not "fail the build if this appears in the log"...
Ability to execute a Maven reactor build on several agents automaticallycancelhelp
Abort builds taking too long to executeaccept Build Timeout pluginhelp
Clean the Maven local repository regularly too save disk space and find out dependency issuesaccept Maven Repository Scheduled Cleanup Pluginhelp
Historical build performance graphsaccept Performance pluginhelp We can fail a build on custom metrics, including failing the build if it takes longer than such past builds, see Build Failure Conditions.
Personal buildscancel But it should be possible to implement an unbreakable build approach using Git branchesaccept Integrated in IDE (IDEA, Eclipse at least)
Build promotionaccept Promotion pluginhelp
Sonar integrationacceptaccept See Sonar Plugin



Get Connected