CI/CD Best Practices for Your DevOps Journey

© 2019 CloudBees, Inc. All Rights Reserved.© 2019 CloudBees, Inc. All Rights Reserved.
CI/CD Best Practices
for your DevOps Journey
November 4, 2019

© 2019 CloudBees, Inc. All Rights Reserved.
Today’s Speakers
CloudBees: Brian Dawson
DevOps Evangelist
@brianvdawson
DevOps.com: Mitchell Ashley
Director of Research
Mitchell Ashley
CloudBees: Doug Tidwell
Technical Marketing Director
Doug3000

Webinar Overview
Agenda
● Beyond DevOps: Software Delivery Management
● Summary of 10 CI/CD best practices
● “Double-Click” on key best practices
● Breaks for Discussion
● Questions and Answers

DevOps Elite Performers
46x
more frequent code deploys
i.e. multiple times per day vs. once a week or less
2406x
faster time to recover from downtime
i.e. less than an hour vs. weeks
2555x
faster lead-time from commit to deploy
i.e. less than an hour vs. more than a week
1/7th
as likely that changes will fail
i.e. fail 0-15% of the time vs. 46-60%
From https://devops-research.com/

But...
Things aren’t perfect.

We still have...
● Disparate, stand-alone software tools
● No common language, data or process sets
● No clear way to ensure we deliver the right thing
Disconnected and Fragmented teams, tools and process

Executive,
Finance
CPO, PM,
Design
Software
Development and Delivery
IT and Engineering
Dev QA Ops
Marketing,
Docs,
Training
Sales
Support,
Services
Software Delivery
It Takes a Village to Truly Deliver Value

Research Design Build Test Deploy Release Observe Support
Sales/MktgSecurity/OpsDev/QA
CPO/Product
Mgmt/ Design
Support/ServicesExec/ Finance
Identify/Plan
UNIVERSAL INSIGHTS
COMMON DATA
Jira
Confluence
Twistlock Jenkins XGitHub
SonarQubeArtifactory Rollout
Twistlock Flow
Splunk
Existing Enterprise Tools
Introducing Software Delivery Management
All functions collaborating
COMMON CONNECTED PROCESS
Slack
Salesforce

We have to Start with CI/CD and DevOps
Technical Concerns
Software Delivery Management
Business Concerns
Code, Build
Release
Value and Impact
Strategy and Revenue
Research Code Build Test Deploy Release Observe SupportIdentify/Plan
CI
CD
DevOps
Test
Full Software Value Lifecycle
Sell

But the reality is...
Far fewer people are truly practicing CI/CD than is widely
reported!
https://www.cloudbees.com/jenkins/devops-and-jenkins-community-survey-2019

The Path to the Future
As the industry positions itself to build on DevOps practices
with a Software Delivery Management strategy…
...it’s more important than ever that we implement CI/CD best
practices, and prepare for the future.

10 CI/CD Best Practices Summary
1. Track work items
2. Use source code management
3. Tags, not Branches
4. Automate the builds
5. Stop the line when the build breaks
6. Validate and test
7. Deploy
8. Improve incrementally
9. Collaboration
10.Create a true DevOps culture

Best Practice #1:
Track Work Items

Track Work Items
Use a system that lets you track everything related to your
release:
● User Stories
● Bugs
● Infrastructure and environment
This is useful for CI and CD, but is absolutely critical as you
move to DevOps and eventually Software Delivery
Management (SDM).

Best Practice #2:
Use Source Code Management

Use Source Code Management (SCM)
Use an SCM tool to track all the changes made for a
release.
A decentralized version control system such as git
A centralized version control system such as SVN
Must consider support for new and legacy systems

Encourage commit best practices
If culture is to not commit frequently, it won’t matter. If
a developer waits three weeks to commit or branches
off for three weeks, they have delayed the integration
and broken the principles
● Commit frequently
● Minimize duration of branches

Consider how triggers that launch builds are initiated.
● Trigger on every commit
● Trigger on developer branch
● Trigger on pull request
● Trigger on merge

Best Practice #3:
Tags, not Branches

Tags, not Branches
Commit or Merge to the trunk frequently, or even better,
always commit to the trunk/master
Developers often branch and maintain changes off of a
trunk to manage releases.
But branching creates complexity that prevents
everyone from working with a single source of truth, and
introduces maintenance overhead
● Use tags to manage releases
● Implement functionality incrementally
● Use feature flags

Best Practice #4:
Automate the Builds

Automate the Builds
Centralize and automate the entire build process
● Compiling the source code
● Packaging the compiled code
● Container images
The build process should run for every commit.

Automate the Builds
The build should run as quickly as possible
The builds should take no more than 5-10 minutes.
Commit should be blocked during build, to support
“stop-the-line” culture. If builds are long developers
defer commits.
● Build
● Code scans, unit test
● Functional tests if possible
Promote the build to extended CI/CD loop for longer
activities

Best Practice #6:
Validate and Test

Validate and Test
Organizations that don’t validate every build are not
practicing CI.
Organizations that do not continuously test are not
practicing CD.
● Manage tests like code or as code
● Fail if the build if test thresholds aren’t met
● Duplicate the production environment as much as
possible

Best Practice #10:
Create a True DevOps Culture

Create a True DevOps Culture
This may be the most difficult practice to implement, but
no DevOps transformation is possible without it.
Starting a successful DevOps journey requires
significant culture change, including:
● Executive support
● Training
● Funding
● A new mindset for everyone: the CIO/CTO,
release managers, engineering managers, the ops
team, and the dev team.
But..start, learn, and improve

Thank You
Q & A

CI/CD Best Practices for Your DevOps Journey

In this document