Good son of Hudson
March 30, 2017

Good son of Hudson

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Jenkins

Jenkins is used across our company. Release Engineering department uses it to provide numerous streams of product component and integration builds, Software Development and Quality Assurance Departments use it as an outstanding Continuous Integration tool to seamlessly install new builds into various environments and to run test automation suites with automatic reports being sent to all stakeholders.
  • Delivery: Jenkins does a perfect job in hands of our Release Engineering department to provide new product builds to numerous projects in timely fashion.
  • Continuous Integration: Quality Assurance team does not start working on a System Test of the new build until it passed an automated Sanity Test in a CI environment.
  • Delivery (again): Development and QA teams no more spending hours looking at terminal screens while installing a new build to target environment and moreover we're now guarded from human errors in this automated process, thus saving precious time.
  • With growing audience of Jenkins within our company the performance and thus usability of the Jenkins control page becoming more and more critical issue. All projects are listed in a single page without paging and it's an issue when you have many hundreds of projects listed...
  • Learning curve is a little too steep: newcomers spend weeks to familiarize themselves with Jenkins. Configuring a project in Jenkins is not as intuitive as we would like it to be.
  • We had a certainly positive impact on Return of Investment after massive implementation of Jenkins throughout organization due to dramatic increase of Release Engineering productivity and achieving much better results in Code Stability thanks to Continuous Integration approach.
Unfortunately I can't weight on decision making points since selection of Jenkins was made prior to me joining the company.
Jenkins is pretty good for Delivery and Continuous Integration which suits current needs of our company pretty well. It provides us with new builds from Release Engineering and supports Test Automation team. It may become slow with growth of amount of projects. However, if you need to focus on Continuous Deployment, you may want to look for other alternatives.

Using Jenkins

It's is fairly good but not perfect.
ProsCons
Like to use
Relatively simple
Easy to use
Technical support not required
Well integrated
Consistent
Convenient
Familiar
Slow to learn
  • Start a new build / AT run
  • History of builds
  • Build logs analysis - slow loading
  • Finding the right project within plain list of hundreds - very slow interface