1. Home
  2. Build Automation Tools
  3. Jenkins Reviews
  4. User Review of Jenkins
Jenkins: The CTCI tool we've all been waiting for
March 14, 2019

Jenkins: The CTCI tool we've all been waiting for

Dylan Cauwels | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Jenkins

We use Jenkins to automate our CD/CI jobs across a variety of applications. It is used by our QA teams to set up automatic testing for software deployments, and by our deployment team to deploy those applications in an automated fashion. This tool is crucial to any DevOps setup and will allow your teams to deploy as often as they would like with minimal effort or employee intervention.
  • Automatic jobs: there are infinite possibilities when it comes to Jenkins. You can run code against any testing suite you can imagine or conjure up. You can deploy applications at any time anywhere, automatically with no human intervention. If a certain stage fails, it will notify the team and your sysadmin of the issue so you can resolve it as quickly as possible
  • Automatic rollback: because of how Jenkins works, it can hold off publishing code and integrate locally to run QA procedures before pushing to deployment. This means that bugs are caught before your servers are updated and prevents a faulty program from affecting your downtime in the first place. Its a game changer for high availability.
  • Very un-intuitive UI can be very confusing for first-time users. It will take a decent amount of time to get any new users comfortable with using the tool
  • It is open-source, but because of this, there is not a lot of support out there for Jenkins-related issues. Because of the possibilities of Jenkins with plugins and customization, there is a decent chance any errors you encounter will be the first of their kind and will have to be solved by you and you alone.
  • Has cut our deployment time drastically by incorporating automatic integration and QA testing into our workflow.
  • Has the ability to deploy our staged code automatically once green-lit by the QA team and the software devs.
Jenkins is the only tool I would consider using for CTCI deployment. Its plugins make it easy to customize to any environment you can conjure up and will always be custom fit to your needs as a DevOps engineer. Other tools have better support but lack the customizability and ease-of-use that we've experienced using Jenkins.
Not the best UI or error notifications, but the customization and performance are unmatched. Its opensource nature is both a curse and a blessing and you'll have to weight the benefits when choosing your CTCI tool. For us, the stakes were never high enough that Jenkins couldn't do everything we wanted and more.
Well suited for any environment that needs to be as automated as possible and is built around the DevOps philosophy. Also, perfect on any cloud infrastructure system as it allows for considerable customization for any type of setup. It allows for applications to be developed in a fast, reliable manner by cutting out the tedious process of integration or basic QA testing. I legitimately cannot think of a scenario where Jenkins would not be useful in improving your software workflow.