Jenkins: From Continuous Integration to Continuous Delivery
Continuous Delivery is the highest form of Continuous Integration. More than just automated deployment, Continuous Delivery involves a mindset change - any build that passes the necessary quality gates can be deployed into production on demand. In this talk, 'Jenkins: The Definitive Guide' author John Ferguson Smart discusses strategies enabling you to turn your Jenkins server into a Continuous Delivery platform, including: - Ways to ensure your builds are always production-ready - automatically! - Parameterizing your builds with style! - Using build pipelines and build promotion in Jenkins to filter out poor builds and streamline the build process. - Reusing artifacts across builds - Rolling back and redeploying previous builds - Deploying to app servers and to the cloud This talk is aimed at developers and build engineers with some previous experience with Hudson/Jenkins.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Mehr von John Ferguson Smart Limited
Mehr von John Ferguson Smart Limited (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Jenkins: From Continuous Integration to Continuous Delivery
- 1. Jenkins From Continuous Integration to Continuous Delivery John Ferguson Smart CEO Wakaleo Consulting
- 2. Who is this guy, anyway? Consulta nt Trainer Mentor Author Speaker Coder John Fer guson S mar t 2
- 3. Continuous Delivery Ge5ng value to the business. Fast. 3
- 4. CI in the clouds DEV INTEGRATION STAGING PROD 4
- 5. Demonstration environment Source code on Github
- 6. Demonstration environment Jenkins instance on Amazon
- 7. Demonstration environment Deploying to CloudBees @RUN
- 8. Demonstration environment Our applicaLon
- 9. Branching into Continuous Delivery or: How I Stopped Worring And Learned to Love Feature Branches
- 10. Branching into Continuous Delivery Feature B Stable Feature A Feature C
- 11. Branching into Continuous Delivery Feature B Stable Feature A Pick and choose what Feature C goes into a release
- 12. Branching into Continuous Delivery The problem with feature branches Everyone needs a canary or two
- 13. Branching into Continuous Delivery Stable IntegraLon
- 14. Branching into Continuous Delivery Stable gameoflife-‐integraLon IntegraLon
- 15. Branching into Continuous Delivery Feature branch integraLon is easy with git and Jenkins
- 16. DEMO The integration branch in action
- 17. Smoke tests “Where there’s smoke, there’s fire” ConLnuous Delivery is impossible without ConLnuous Quality
- 18. Smoke tests gameoflife-‐integraLon DEV gameoflife-‐smoke-‐tests INTEGRATION STAGING PROD
- 19. Smoke tests Smoke Tests can also be Automated Acceptance Tests gameoflife-‐integraLon DEV gameoflife-‐smoke-‐tests
- 20. DEMO Smoke Tests in Action
- 21. Continuous Delivery Deliveries when the business needs them
- 22. Continuous Delivery Feature B Stable gameoflife-‐default gameoflife-‐code-‐quality 1.2.3 gameoflife-‐release-‐candidate STAGING gameoflife-‐smoke-‐tests
- 23. DEMO Producing a release candidate
- 24. Build Pipeline Pushing your code into producLon
- 25. Build Pipeline Stable gameoflife-‐default gameoflife-‐code-‐quality gameoflife-‐release-‐candidate STAGING gameoflife-‐smoke-‐tests 1.2.3 gameoflife-‐deploy-‐to-‐prod PROD gameoflife-‐smoke-‐tests
- 26. Build Pipeline
- 28. THANK YOU! John Ferguson Smart Email: john.smart@wakaleo.com Web: h`p://www.wakaleo.com Twi`er: wakaleo