1. 1

2. Continuous Delivery
with Cloud Foundry
2

3. CloudCredo
London
3

4. 4
realness ->
time->
Deployment Pipeline
4

5. Refresher:
Why are we doing this?
5

6. 6
⟳ 6

7. Cloud Foundry
7

8. Consistent Interface for Deployment
$ cf push
8
8

9. Avoid making breaking changes that
delay feedback
9
9

10. cloudfoundry.com »
10
Feedback
10

11. decomposed the application into
services »
11
Feedback
11

12. custom release »
12
Feedback
12

13. multiple platforms, multi-region »
13
Feedback
13

14. 600,000
transactions in 7 hours
14
Feedback
14

15. 500
user journeys every second
15
Feedback
15

16. 10,000
call center operators
16
Feedback
16

17. ♥beat
17
Feedback
17

18. Production-like
Environment
18

19. Build and scale new environments
repeatably
19
Environments
19

20. Perform load testing within your
pipeline
20
Environments
20

21. Externalizing Configuration
21
Environments
21

22. 12factor.net
22
Environments
22

23. Reproducible Environments
23
Environments
23

24. BOSH
24
Environments
24

25. Artifact Repositories
25
Environments
25

26. Blue / Green Deployments
26
Environments
26

27. Things to watch out for
27

28. Manual application changes
28
Gotchas
28

29. Branching Deployments
29
Gotchas
29

30. Adding infrastructure
code to the pipeline
30

31. 31
Application Code
Infrastructure Code
Base OS
Your service
31

32. ✔ Validation of BOSH Manifests
32
Infrastructure code
32

33. ⇑ Automate upload of BOSH releases
33
Infrastructure code
33

34. ⇓ Automate updates from upstream
releases, binaries
34
Infrastructure code
34

35. Key Takeaways
• Cloud Foundry makes building continuous delivery pipelines
much easier.
• Cloud Foundry makes it easy to Do the Right Thing.
• PaaS abstraction allows you to grow from small-scale to
large scale and maintain a steady heartbeat of delivery.
35
35

36. Thanks!
andrew@cloudcredo.com
36