Release pipeline orchestration has become an essential foundation for successfully coordinating and scaling Continuous Delivery across the enterprise. But in order for any DevOps change to succeed – be it cultural or process-oriented – enterprises must consider the diverse needs and preferences of their teams. They need processes and tools that match their capabilities and work style.
There’s a lot of buzz now about managing releases as code. Developers love being able to define everything in manageable artifacts. But managing pipelines as code is only a part of a much bigger picture, not the core solution. In this live webinar learn best practices for release orchestration using flexible approaches that work for team members across the enterprise.
Tune in to this on-demand webinar to learn more about these best practices as well as:
How to bring intelligence, automation, visibility and control to your release pipelines.
Pitfalls to avoid when using code as your primary method to manage releases.
How you can ensure compliance requirements in your release process are met regardless of the method used.
7. 7 Copyright 2017. Confiden4al – Distribu4on prohibited without permission
A Chaotic Release Process
▪ Copious spreadsheets, Word docs and emails, often
with everyone working from different versions
▪ Daily status meetings, often early in the morning
▪ Frenzied phone calls to get the latest status and
track down issues
▪ No visibility across the business
▪ No good way to capture changes for audit purposes
!
13. 13 Copyright 2017. Confiden4al – Distribu4on prohibited without permission
2 Modes - Triggering
• “When requested by the business owner”
• “After the sprint demo, if approved”
• Regularly, but not to a precise schedule
• “When commit is merged to main branch”
• “With nightly build”
• From listening for code-level events
“Scale by responding to many different drivers!”
Automation DrivenProcess Driven
18. 18 Copyright 2017. Confiden4al – Distribu4on prohibited without permission
Summary
1. Continuous Delivery
doesn’t scale without
release orchestration
2. Leverage multiple
skillsets and drivers
to scale successfully
▪ Enterprises that implement release
orchestration often reduce the time to
release software from months down to
days, or even hours.
▪ Dual-mode release automation removes
bottlenecks and increases resource
utilization.
▪ Complex heterogeneous software
deliveries.
Outcomes: