SpringOne Tour by Pivotal Continuous Deployment to the Cloud by Topher Bullock

1. © Copyright 2017 Pivotal Software, Inc. All rights Reserved. Version 1.0
Topher Bullock
Staff Software Engineer, Pivotal
Continuous Deployment
to the Cloud

2. Why do we continuously do things?

3. Agile & Lean
Traditional
Risk
Time
De-risking Your
Product
The sooner you release to prod
(your stakeholders) the faster you
can measure the impact of new
features.

4. Lots of people
are doing it!
1000+ deployments/day, every 11.6
seconds (2011) [1]
Up to 50 deployments per day [3]
40,000+ monthly deployments to
OneOps platform [2]

5. Even enterprises
are doing it!
Liberty Mutual
https://content.pivotal.io/slides/crossing-the-ci-cd-devops-chasm
Total number of builds per month
Total number of
deploys per month

6. Lean Product
LEARN BUILD
MEASURE

7. Building is Hard
LEARN BUILD
MEASURE

8. When you have large

9. When you have large, distributed teams

10. When you have large, distributed teams. With complex
processes

11. When you have large, distributed teams. With complex
processes, and business rules.

12. Deploy faster, and break things
before you deploy
“move fast and break things”

13. Concourse CI
An open-source continuous thing-doer.

14. Built on the simple mechanics of resources, tasks, and
jobs, Concourse presents a general approach to
automation that makes it great for CI/CD
Concourse CI

16. Concourse’s CI/CD
A Real Pipeline

17. Deploy + Test RC on supported
platforms
Bundle up each component into
an RC
➔ Integration
The Concourse
Team’s Pipeline
➔ µ Unit Tests
Unit Test each component of
Concourse
➔ Deployment

18. Jobs
plan:
➔ task:
➔ get:
➔ put:
>_
Example: a minimal single job pipeline
A list of build steps to
execute

19. Resources
➔ in
➔ check
➔ out
triggered by a get step
triggered by a put step
periodically triggered
git fetch 1d0d713
git pull @1d0d713
1d0d713git push
Interact with the external
world.

20. A Tale of Two Microservices
Some Toy Examples

21. ‘Passed’
Constraints
Pipelines are built around the
safety of passing around versions
of resources.
The structure of jobs in a pipeline is
entirely defined by this version
gating
When a new commit fails a buid of a job, the passed
constraints will ensure that commit doesn’t pass along
to the later stages of thew pipeline
abc123 abc123

22. Rapid Local
Iteration
This will run your code in exactly the same way it
would run in your pipeline, without you having to
repeatedly push broken commits until it works.
The fly execute command executes
a task as a one-off build, with your
local changes.

23. A CI/CD Success Story
Pipelines as Code

24. Cover w/ Image
Spring Cloud Pipelines
● Creation of a common deployment
pipeline
● Propagation of good testing &
deployment practices
● Speed up the time required to deploy a
feature to production
● A common way of running, configuring
and deploying applications lowers
support costs and time needed by new
developers to blend in when they
change projects.
● Cloud Foundry PaaS support
● Kubernetes PaaS support

25. Fly your friendly Concourse pipeline
Flexible integration
of resources
Simple modeling of
components
Pipeline status is
immediately visible
Build components are
expressed as code

26. Follow the Concourse Team
https://github.com/concourse
https://medium.com/concourse-ci
https://discordapp.com/invite/MeRxXKW

27. Transforming How The World Builds Software
© Copyright 2017 Pivotal Software, Inc. All rights Reserved.