Jenkins CI/CD
Overall Satisfaction with Jenkins
We primarily use Jenkins as part of our build infrastructure for compile and build, typically executing mavens builds but also ant scripts for more complex tasks and workflows
Pros
- Is an excellent automation container
- Is excellent at integration with many other tools and services
- Is superbly well supported in the dev community with over 1k plugins
- Is very easy to recruit for, having high market penetration and lots of candidates with experience
- Has a number of security models to suit any enterprise or small user
- Is very scalable both horizontally and vertically
Cons
- History retention is an area that should improve
- Trend analysis should be better supported in the core product
- Dashboards need to be better provisioned in the core product
- Deployment automation is the biggest gain. You can plug anything into anything using Jenkins as the UI
- Simplifying complex tasks via UI
- Capturing complexity and removing/reducing key man dependencies
Comments
Please log in to join the conversation