Likelihood to Recommend
Jenkins is open source, thus has a large number of plugins rolled out already. All major VCS, SCM, Git, and Maven applications support Jenkins. They even support Docker which is trending in DevOps nowadays. It has more than 50 APIs and plugins to work on. Thus, it is always appropriate to have Jenkins when you have a distributed workforce and to sync with everyone. To avoid synchronization problems in the distributed workforce and development, we use Jenkins. Code pushed to VCS can be built over another system so as to deploy in the production/release.
Team Lead in Information TechnologyInformation Technology and Services Company, 11-50 employees
- Jenkins abstracts the build/compile process, so that a local development machine doesn't need to constantly be updated or contain all of the libraries/packages required for more extensive builds.
- Jenkins allows extremely customized and parameterized builds, allowing non-technical coworkers to initiate builds and set their own parameters.
- Jenkins has a large collection of plugins that can retrieve and send build data/artifacts to/from various services, and can also hook into many popular apps like Slack and Hipchat.
- Sometimes installing the wrong plugins ends up with Jenkins in a non-startable state.
- When there is a huge number of builds, loading the Jenkins UI takes minutes. Sometimes times out as well.
- Lacking user level minute audit logging. It's difficult to find out which users installed/upgraded plugins.
- There were cases where jobs were in a hung state and could not be aborted as well. Jenkins restart was the only solution.
Engineer in EngineeringComputer Software Company, 1001-5000 employees
Based on 1 answer
It's is fairly good but not perfect.
Analyst in Quality AssuranceComputer Software Company, 1001-5000 employees
Based on 6 answers
The biggest drawback of Jenkins I think is lack of backup/baseline the jobs, so we could lose our whole jobs by accidentally deleting it.
TeamCity is another viable option for Continuous Integration/Development. We picked Jenkins in this case because there was a lot of support for Amazon CloudFormation and other AWS integrations which fit the task at hand. For just straight compiling Microsoft based builds, TeamCity was a bit easier to use but was a bit more lacking in the AWS build options.
Return on Investment
- Deployment automation is the biggest gain. You can plug anything into anything using Jenkins as the UI
- Simplifying complex tasks via UI
- Capturing complexity and removing/reducing key man dependencies
Premium Consulting/Integration Services—
Entry-level set up fee?