Drive your Continuous Integration Pipelines via Scripting with Jenkins
Updated August 27, 2023
Drive your Continuous Integration Pipelines via Scripting with Jenkins
Score 10 out of 10
Vetted Review
Verified User
Overall Satisfaction with Jenkins
We use Jenkins in our continuous integration pipelines. With Jenkins, we build and test our microservices. We also make extensible use of the plugin capability (we also develop and maintain internal plugins) to cover complex build/testing scenarios.
- Extensive documentation
- Big community and popularity
- Easy to extend and customize
- Improve configuration portability
- Improve scalability
- Increase interoperability with containers
- Introduce ways to update common dependencies automatically (eg Docker)
- Scripting
- Maturity
- Documentation and popularity
- We use the plugin & scripting capabilities to reuse the pipeline components in multiple services
- Our team has experience working with JVM services and because Jenkins uses the JVM as runtime so we use our knowledge to troubleshoot, tune and monitor the CI
GitLab CI and GitHub Actions are other powerful options in the market also with a rising popularity and high interoperability with their respective platform.
But Jenkins is still a good option for complex pipelines that require scripting and logic. Also, Jenkins uses as runtime the JVM so if your team is already familiar with the JVM stack and related monitor tool is also an option to take in mind.
But Jenkins is still a good option for complex pipelines that require scripting and logic. Also, Jenkins uses as runtime the JVM so if your team is already familiar with the JVM stack and related monitor tool is also an option to take in mind.
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