Continuous delivery using jenkins
3 likes1,197 views
This document discusses the importance of continuous delivery using Jenkins. It introduces continuous integration and continuous delivery, explaining that continuous integration provides fast feedback on code changes while continuous delivery provides feedback on production readiness. It outlines how to set up a build pipeline in Jenkins to guarantee production readiness and make releases risk-free and automated. The document emphasizes that continuous delivery satisfies customers through early and frequent delivery of software and encourages teams to take responsibility for releases through continuous improvement.
Continuous delivery using jenkins
- 2. Why Continuous Delivery is important Intro to Jenkins and Build Pipeline Setup Takeaways
- 5. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software First Principle of Agile Manifesto
- 9. Fast, automated feedback on the correctness of your application every time there is a change to code Continuous Integration
- 10. Continuous Integration in Action
- 12. Continuous Delivery Fast, automated feedback on the production readiness of your application every time there is a change — to code, infrastructure,or configuration.
- 14. Build Pipeline Guarantees the production readiness Makes release a risk-free automated affair Tie release with business decisions
- 15. Build Pipeline in Action
- 16. Feature Branches
- 19. Summary Everyone is responsible for Release Build Quality In Continuous Improvement
- 20. If humans start doing those repetitive tasks which computers are designed to do, all the computers get together late at night and laugh at you Neal Ford
- 21. Next Steps How long would it take you to deploy a change that involves just one single line of code? Can this be done on a repeatable, reliable basis? Mary and Tom Poppendieck
- 23. Thanks !! Questions? http://bit.ly/JenkinsCDWorkshop @leenasn @akshaykashain continuousdelivery.in