Stairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
summary
Continuous delivery reduces defects and cycle time by automating build, package and deployment steps using Jenkins (claims 80% CI share), storing artifacts in Artifactory/Nexus, and managing DB changes with Liquibase; a UK government pipeline shrinks deploys from 6 days to 6 hours by automating each component. Recommendations include build once deploy anywhere, choosing directive vs convergent deployment per topology, using Jenkins workflows and parameterized matrices, keeping templates with environment variables, and logging approvals for compliance.
AI-written summary · about
chapters (25)
- 0:00Intro
- 2:32Agenda
- 3:08Continuous Delivery
- 4:28Deployment
- 7:19Why Continuous Delivery
- 9:23Tools for Continuous Delivery
- 10:30Automate Everything
- 13:47Deployment Paradigm
- 15:52Deployment Type
- 16:51Build Once Deploy Anywhere
- 18:05Deployment Model
- 22:16Model Driven Deployment
- 23:47Prerequisite Resource Environment Testing
- 25:24Automated Testing Strategy
- 27:21Deployment Approval
- 29:39Deployment Approval Process
- 30:46Rollback Strategy
- 34:52Metrics Analytics
- 37:42Summary
- 38:56Examples
- 39:53Simple Deployment
- 41:35One Cluster
- 41:50Production topology
- 42:21Convention over configuration
- 43:24Key takeaways
related talks
44mStairway to Heaven: 10 Best Practices for Enterprise Cont. Delivery w/ Jenkins
24mWhy, What, and How of Continuous Delivery
24mCI/CD Best Practices to Deliver Software Faster
45mBuilding Your Continuous Delivery Toolkit
27mAutomation, Innovation and Continuous Delivery
51mBetter software, faster: principles of Continuous Delivery and DevOps
33mMaking Strides towards Enterprise-Scale DevOps...w/ Jenkins in Your Tool Chain- 45mBuilding Your Continuous Delivery Toolkit