DevOps insights on Jenkins for CICD.
May 22, 2023
DevOps insights on Jenkins for CICD.
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Jenkins
For nearly the last decade, we have used Jenkins as an automated build tool platform. My company does a lot of in-house app development. Like many other IT shops, Jenkins is a key component of continuous integration continuous deployment (CICD) pipelines. Allows us to schedule jobs automate film processes, deployment processes, server bounces, etc. It's capable of doing a myriad of options, anything from simply pushing a shell file to run token replacement, ant or Maven scripts, automated scheduled builds, on-demand execution, and trigger-based runs. We can even use it to interface with AWS for deployments to the cloud.
- It's fantastic at cutting down on manual steps for building and deploying ear and war files.
- Excellent tool for scheduling deployments.
- Trigger-based builds, such as when code is checked into a repository like GIT, are a strong suit of this tool.
- It can sometimes be difficult to navigate, especially when you're trying to drill down into configurations that are sourced outside of your job but referenced by the job you're designing.
- CICD
- The relative ease of use.
- Scalability.
- I can't give any hard numbers, but I can say that our turnaround time for deployments is increased greatly And that we are able to execute multiple deployments to various environments swiftly.
Honestly, we use Jenkins for pretty much everything exclusively, so it's hard to compare.
Do you think Jenkins delivers good value for the price?
Yes
Are you happy with Jenkins's feature set?
Yes
Did Jenkins live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Jenkins go as expected?
Yes
Would you buy Jenkins again?
Yes