All enterprises want to increase the speed of software delivery to get new products to market faster. The means for achieving this is often through the practice of continuous integration/continuous delivery. But speed alone isn’t enough—teams also require the ability to pivot when conditions change. They must ensure their software is stable and reliable, and be able to roll out patches and other security measures quickly and at scale. A cloud-native platform coupled with test-driven development and CI/CD practices can help make this a reality. In this webinar, 451 Research’s Jay Lyman presents the results of his research into cloud-native platform requirements for enterprise CI/CD and DevOps success. Pivotal’s James Ma joins Lyman to discuss best practices from DevOps teams charged with running and managing cloud-native platforms, including applying CI/CD to the platform itself. Speakers: James Ma, Pivotal and Jay Lyman, 451 Research

1. © Copyright 2017 Pivotal Software, Inc. All rights Reserved. Version 1.0
Platform Requirements for CI/CD Success
– And the Enterprises Leading the Way
James Ma, Pivotal Jay Lyman, 451 Research
@PioverPi @RipCityLyman
June, 2018

2. Enterprise CI/CD & DevOps:
• Enterprise priority with digital transformation, cloud modernization
• The need for a holistic approach
• Beyond devs and ops – additional key stakeholders
• The need to run across hybrid infrastructure
• Drivers, challenges, outlook
2

3. Report: Voice of the Enterprise: Cloud Transformation, Vendor Evaluations - Quarterly PowerPoint Charts and Figures
Source: 451 Research, Voice of the Enterprise: Cloud Transformation, Vendor Evaluations 2017 © 451 Research, 2000-
2017
Q: Please describe the level of usage within your organization for
each of the following technologies.

4. CLOUD, HOSTING AND MANAGED SERVICES
BUDGETS AND OUTLOOK 2017
CLOUD, HOSTING AND MANAGED
SERVICES: BUDGETS AND OUTLOOK
2017
Source: 451 Research, Voice of the Enterprise:
Cloud, Hosting and Managed Services, Budgets
and Outlook 2017
Q18. What are the most
important goals for your
organization’s IT environment
over the next 12 months? Please
select up to 2.
4
53%
42%
32%
30%
23%
2%
Respond faster to business needs
Reduce costs
Improve reliability and availability
Identify threats and minimize risk
Expand/deploy new capacity
Other
Percent of Sample
n = 657
Important IT Environment
Goals
Cloud, Hosting and Managed Services Users

5. Lot’s 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]

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

7. Enterprises are
deploying faster
Scotiabank deploys over 3,000 times a month
in 10 months after adopting PCF.
Garmin deploys to production 1,100 times per
months.
The Home Depot ships to production 1,500
times a month, and 17,000 times a month to all
environments.
Liberty Mutual deploys 1,000 times a day to
production on 2,500 daily builds.
But what is their secret?

8. Q: Beyond IT operations and developers, what stakeholders are involved in your modern
IT management or DevOps initiatives and strategies?
8
64%
46%
66% 66%
1%
0%
10%
20%
30%
40%
50%
60%
70%
Database administrators
and data analytics teams
Lines of business
managers
Technology center of
excellence or similar
group
Security Other (please specify)
N = 450

9. Report: Voice of the Enterprise: Cloud Transformation, Vendor Evaluations - Quarterly PowerPoint Charts and Figures
Source: 451 Research, Voice of the Enterprise: Cloud Transformation, Vendor Evaluations 2017 © 451 Research, 2000-
2017
Use of different cloud environments over the next two years:
68% leveraging multiple cloud environments; 17% seamless hybrid

10. Multi-Cloud with BOSH + CPI

11. Source: 451 Research, Voice of the Enterprise: Cloud, Hosting & Managed Services, Workloads and Key Projects 2018
Q15. When developing cloud-native software, which, if any, of the following approaches does your organization take to designing that software?
11
32%
30%
22%
17%
Design it to run effectively on any cloud environment
Design it to run on a specific public cloud environment
Design it to run effectively on any public cloud environment
Design it to run on our own private cloud
% of respondents (n = 266)
Approaches to cloud-native software development
Respondents developing cloud-native or cloud-enabled software

12. vSphere OpenStack AWS
Google
Cloud
Azure &
Azure
Stack
Shared Services
Shared Security
Shared Networking
Logging & Metrics / Services Brokers / API Management
Credhub / UAA / Single Sign On
VMWare NSX
Embedded Operating System (Windows / Linux)
Application Code & Frameworks
Buildpacks / Spring Boot / Spring Cloud / Steeltoe
PAS
Pivotal Application
Service
PKS
Pivotal Container
Service
PFS
Pivotal Function
Service
Pivotal Services
Marketplace
Pivotal and
Partner Products
Any App
Every Cloud
One Platform
Concours
e
PCF 2.0 — for everything
that matters

13. Q: What are the primary drivers for your
organization’s application and/or IT modernization?
13
230
235
195
177
184
133
193
3
0
50
100
150
200
250
Cloud migration Digital transformation Data center
consolidation
Deliver customer
value faster
Data-driven
applications and
workloads
Shift to a more
software-centric
business
Cost Other
N = 450

14. It’s a lot of work, but it pays off
2017
State of DevOps
Report
By Puppet and
DORA [1]
“High” IT performers “Low” IT Performers
Deployment
frequency
On-demand
1 week - 1 month
(quarterly or worse)
Lead time for
changes
< 1 hr 1 week - 1 month
Mean time to
recovery
< 1 hr 1 week - 1 month
Change Failure
Rate
0 - 15% 31 - 45%
[1] https://puppet.com/resources/whitepaper/state-of-devops-report

15. Q: What are the biggest challenges preventing IT modernization in your company?
Please rank three in order of importance with the most important as number one.
150 50 100 150 200 250 300
Total
1
2
3
Internal resistance to change (G)
Doesn’t solve business requirements or
problems (F)
Lack of skills for cloud applications (E)
Existing deployment and management of
applications is sufficient (D)
Ability to run production applications in
the cloud (C)
Compliance and regulatory issues (B)
Security (A)
N = 450

16. Cerner: Modeling Processes Into Pipelines

17. Cerner: Modeling Processes Into Pipelines
“The cool thing you can do inside of Concourse is
that all these ISO process pieces and artifacts
can just become a Resource.”
- Greg Meyer, Cerner Corp.

18. Source: 451 Research, Voice of the Enterprise: Cloud, Hosting & Managed Services, Workloads and Key Projects 2018 18
Primary environment used for operation today & in two years’
time
Respondents identifying workloads as currently in place
38%
19%
14%
11% 10%
8%
0%
17%
29%
14%
19%
14%
4%
1%
On-premises
“traditional”
resources and
infrastructure
Software as a service
(SaaS) and hosted
applications
On-premises private
cloud IT resources
and infrastructure
Infrastructure as a
service
(IaaS)/platform as a
service (PaaS)/public
cloud
Hosted private cloud Hosted, non-cloud
infrastructure
None
Today (n = 650) In two years (n = 601)
Q18. Which of the following best describes the primary environment used to operate your organization’s (Workload) today?
Q19. Which of the following best describes the primary environment in which your organization’s (Workload) will be operated two years from now?

19. Continuous thing-doing at Pivotal

20. Embedded OS
(Windows & Linux)
NSX-T
CPI (15 methods)
v1
v2
v3
...
CVEs
Product Updates
Java | .NET | NodeJS
Pivotal Application
Service (PAS)
Application Code &
Frameworks
Buildpacks | Spring Boot | Spring Cloud |
Steeltoe
Elastic | Packaged Software | Spark
Pivotal Container
Service (PKS)
>cf push >kubectl run
Pivotal
Network
“3Rs”
Github
Concourse
Concourse
Pivotal Services
Marketplace
Pivotal and
Partner Products
Continuous
delivery
Public Cloud
Services
Customer
Managed
Services
OpenServiceBrokerAPI
Repair
— CVEs
Repave Rotate
— Credhub
Azure &
Azure Stack
vSphere OpenStack AWS
Google
Cloud
Azure &
Azure Stack

21. Cover w/ Image
Why TDD
Writing a test first helps:
● Gain the CONFIDENCE you need to
REFACTOR your code to keep it
CLEAN so that you can GO FAST
FOREVER.
● Tease out and think through your APIs.
● Clarify exactly what behavior you’re
trying to build.
● Know when you’re done.
● Triangulate on simple, maintainable
implementations, by making each test
pass one by one.
● Write just enough code to make each
test pass.Matthew Kane Parker, Head of Engineering, Pivotal Labs
https://builttoadapt.io/why-tdd-489fdcdda05e

22. Cover w/ Image
Making Defects Visible
● Green means good
● Red indicates a problem
● Yellow indicates a step is actively
executing
● Teams quickly aligned on issues with
context

23. Culture of shared responsibility for well-functioning
code
https://springoneplatform.io/sessions/take-devops-to-11-and-sprinkle-cloud-on-it-with-rainbows-and-unicorns

24. Continuous Thing-Doing with Concourse CI

25. Pipelines are defined as a single
declarative config file composing
together just three core concepts.

26. Resources
● Track versions of
external artifacts used for
CI / CD
● Any entity that can be
checked for new versions,
pulled down at a specific
version, and/or pushed to
● Can by one of many types
of built in resources; git
repositories, Amazon S3
Buckets, Docker Images,
or a custom
implementation
Three Core Concepts
Tasks
● Allow the execution of
arbitrary scripts against a
set of resources.
● Can output directories
representing a new
resource version.
● Run in a container using a
configurable container
image.
Jobs
● Represent the plan for a
build step within a
pipeline.
● Can contain operations
against resources, or
tasks as steps.
● Builds of a job’s plan can
be triggered manually or
trigger on new versions of
resource.

27. Examples

28. 3-box pipeline

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