No two companies' build pipelines are alike. Some are cloud-first and some work entirely behind the firewall. In each type of organization, and in all of those in-between, there is a need to efficiently scale up and out their continuous delivery infrastructure as the organization matures.
Technical Account Managers (TAMs) like Matt Shelton work with loads of enterprise customers and get a birds'-eye view of the myriad challenges they face. Join him for a discussion of scaling continuous delivery while balancing the demands of risk and compliance against the pressures of a shrinking time to market. He'll show how products like Bamboo, Bitbucket Pipelines, and per-build containers align best with different organizational needs in the pursuit of DevOps perfection.
15. As Cloud Native environments get more and more attraction, the
tooling around these environments continue to evolve to fit the
various needs.
MUSTAFA AKIN, ATLASSIAN OPSGENIE
The objective is to improve speed and stability by optimizing the
pipeline by leveraging Cloud Native model at each step, from
coding to production, by making use of tools, such as containers
and orchestrators, combined with additional tooling.
Cloud Native is a new approach to build and run applications that
can leverage the cloud computing delivery model.
24. Who?
- Newer non-public companies
- Industries that move very quickly
High
Low
Low High
RiskTolerance
Flexibility
25. Driving force is the team
- Team or product drives technology decisions.
- Teams may build/run it themselves.
Who?
- Newer non-public companies
- Industries that move very quickly
High
Low
Low High
RiskTolerance
Flexibility
26. Driving force is the team
- Team or product drives technology decisions.
- Teams may build/run it themselves.
Other Considerations
- Cloud deployment
- Prepare for future habits
- Shared Responsibility
Who?
- Newer non-public companies
- Industries that move very quickly
High
Low
Low High
RiskTolerance
Flexibility
35. Who?
- Public companies
- Startups in healthcare, finance, etc.
High
Low
Low High
RiskTolerance
Flexibility
36. Driving force is team of teams
- Innovation weighed against business needs
Who?
- Public companies
- Startups in healthcare, finance, etc.
High
Low
Low High
RiskTolerance
Flexibility
37. Driving force is team of teams
- Innovation weighed against business needs
Other Considerations
- Cloud deployment?
- Process gates
- Shared Responsibility Model
Who?
- Public companies
- Startups in healthcare, finance, etc.
High
Low
Low High
RiskTolerance
Flexibility
38. DevOps Culture
Shift Left
Shorten Mean Time to Resolution
Bitbucket + Bamboo
Federate Bamboo
w/ Elastic Agents and
Bitbucket Code Insights
41. Who?
- Public companies
- Industries with tight regulatory controls
- Have been burned before
High
Low
Low High
RiskTolerance
Flexibility
42. Driving force is risk mitigation
- Streamlined and standardized over creative
- Compliance controls rule the day
Who?
- Public companies
- Industries with tight regulatory controls
- Have been burned before
High
Low
Low High
RiskTolerance
Flexibility
43. Driving force is risk mitigation
- Streamlined and standardized over creative
- Compliance controls rule the day
Other Considerations
- Less public more private cloud
- Shared Responsibility Model may be too risky
Who?
- Public companies
- Industries with tight regulatory controls
- Have been burned before
High
Low
Low High
RiskTolerance
Flexibility
54. We do peer review because that is how
you build quality in agile - but we enforce
peer review because it helps us manage
the risk and also meet our compliance
obligations.
GUY HERBERT, ATLASSIAN RISK FUTURIST
56. Cascading Peer Review
Code Review
Enforce correct makeup of
reviewers as well as number
of passing builds
57. Pipeline Review
Review Specs and
downstream impacts
Cascading Peer Review
Code Review
Enforce correct makeup of
reviewers as well as number
of passing builds
58. Pipeline Review
Review Specs and
downstream impacts
Cascading Peer Review
Container Review
Review and automate scans
Code Review
Enforce correct makeup of
reviewers as well as number
of passing builds
61. Who?
- Mature DevOps-embracing organizations
- Change and Risk understood and embraced
High
Low
Low High
RiskTolerance
Flexibility
62. Driving force is culture
- People/Practice are embraced over a tool
- Requires a lot of self-awareness and honesty
Who?
- Mature DevOps-embracing organizations
- Change and Risk understood and embraced
High
Low
Low High
RiskTolerance
Flexibility
63. Driving force is culture
- People/Practice are embraced over a tool
- Requires a lot of self-awareness and honesty
Other Considerations
- Choose tools to mirror flexibility
Who?
- Mature DevOps-embracing organizations
- Change and Risk understood and embraced
High
Low
Low High
RiskTolerance
Flexibility
65. DevOps Culture
Agility at Scale
Blameless Review
All the things!
Bitbucket + Bamboo + Cloud
Utilize a hybrid approach based on
strong controls and flexible practices