Continuous Integration Software Selection
Last modified by Vincent Massol on 2020/05/10 13:37
Description
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 Cases | Jenkins | TeamCity |
|---|---|---|
| Be able to have a display for running our Selenium tests |  XVNC plugin | 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) | Scriptler plugin with Groovy script |  |
| Easily remove all jobs for a given branch (for cleanup) | Scriptler plugin with Groovy script | |
| Don't send emails on false positives | Scriptler + Mail Ext + PostBuild plugins | 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 automatically |  | |
| Abort builds taking too long to execute | Build Timeout plugin | |
| Clean the Maven local repository regularly too save disk space and find out dependency issues | Maven Repository Scheduled Cleanup Plugin | |
| Historical build performance graphs | Performance plugin | 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 builds | But it should be possible to implement an unbreakable build approach using Git branches | Integrated in IDE (IDEA, Eclipse at least) |
| Build promotion | Promotion plugin | |
| Sonar integration | | See Sonar Plugin |
