Jenkins: The defacto standard build tool
Mark Carpenter | TrustRadius Reviewer
February 07, 2019

Jenkins: The defacto standard build tool

Score 10 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Jenkins

Jenkins is our standardized build tool for all our software teams. It has allowed us to move to a standardized continuous integration development cycle rather than the ad-hoc build and deploy structure that was used in the past. Having the ability to manage all our builds from a single web platform has been great for the management of our build process. We now have the ability to easily pull build logs and to determine where individual builds we're deployed. Jenkins has been highly beneficial for our company.
  • Manage continuous integration. It can be set up.
  • Allows a single point of access for all our companies build information.
  • It is also highly configurable and allows our individual teams to customize the builds as necessary.
  • We have had some trouble with using Ansible with Jenkins to allow a 'pipeline' build. This points to a potential area Jenkins could improve by allowing a clean way to define build pipelines. It has the ability to define promotions to specific environments but the UI for that feature is not intuitive.
  • There were a few examples where saving build configuration changes would not actually save the changes.
  • Jenkins is a great tool, but the UI for the list of projects becomes hard to navigate when you have a large number of projects. It could use an updated design.
  • Jenkins has reduced our time to market since we can integrate various deployments and test suites directly into the build
  • Jenkins has reduced the training time required for our new engineers. Since this is the defacto build tool, most of our new hires already understand how to use it.
  • Jenkins is also a free tool which provides these benefits without costing the company, although there are companies that provide support.
Microsoft Azure includes Azure Pipelines as part of its suite of tools. It is an adequate tool but tends to be overly complicated. I find that Jenkins is a much simpler tool to use.
FF4J (Feature Flipping for Java), Togglz, Ansible
I have never had a performance concern with the Jenkins UI. Everything loads in a reasonable amount of time even when performing complex builds. We have integrated numerous unit testing, detecting, and coverage tests to our builds and Jenkins is able to easily handle the load we put on it.
Jenkins is well suited to be used in any build use case. I consider Jenkins to be the gold standard for build tools and should be the primary choice for any build unless there are mitigating circumstances that require another tool.