devops best practices: managing and scaling release automation using visual and code-centric methods

DevOpsBestPractices:ManagingandScalingReleaseAutomationintheEnterpriseUsing Visual and Code-centric Methods January 31, 2017

2 Copyright2017.Confiden4al–Distribu4onprohibitedwithoutpermission

Housekeeping

▪ This webinar is being recorded

▪ Links to the slides and the recording will be made available after the presentation

▪ You can post questions via the GoToWebinar Control Panel


Meet Your Presenters

Tim Buntel VP of Products, XebiaLabs

Vincent Partington CTO, XebiaLabs


Agenda

4

•  Release Pipeline Orchestration •  Dual-Mode Enterprises

•  Low-code/no-code •  Code-centric •  Hybrid

•  Demonstration •  Questions & Discussion


DevOps in Theory: an Automated Pipeline

•  Build •  Integrate •  Test •  Provision • Deploy • Operate


DevOps In Practice: a Complicated World

•  Security • Compliance • Marketing •  Program Management •  Business Impact •  Etc.

Much still manual…

BUT…


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

!


So Many Separate Tools!


Automation and Orchestration


Maturing DevOps/CD in the Enterprise

Today

Dev + Ops Needs

Management + Business Needs

Visibility/ Analytics Decision Support Feedback

Organization’s Needs

Enterprise Requirements

Integrations Process Complexity Heterogeneous Systems Compliance Security Scale

Automation Efficiency Speed Error reduction


Two Factors for Scaling

Skillsets Triggering Who can do the work?

What drives the work?


2 Modes - Skillsets

•  GUI Based •  Release Managers •  Risk & Compliance

•  Developers •  Code Artifacts •  Standard Code Workflows

“Scale by leveraging the skills you already have!”

Code-Centric GUI-Centric


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 Driven Process Driven


Scaling it All

Process Driven

Code-centric

GUI Centric

Event Driven


XebiaLabs + CI


Scaling it All

Process Driven

Code-centric

GUI Centric

Event Driven

•  XL Release •  Xfile

•  Xfile •  Jenkinsfile

•  XL Release •  Xfile •  Jenkins


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:

devops best practices: managing and scaling release automation using visual and code-centric methods

Software