Sensible defaults for CI and CD in 2019

•

3 likes•1,243 views

CI and CD are nothing new. But learning more about how to do them better is where we should be focusing our energy – the goal is after all to enhance our ability to deliver value.

Technology

1
1
SENSIBLE DEFAULTS FOR CI/CD IN 2019
Charles Korn

Sensible defaults for CI/CD in 2019
Charles Korn

6
Mean time  
to recovery
Deployment
frequency
Lead time  
to change
Change  
failure rate

7
Time
Seconds Minutes Hours Days Weeks
Dev working locally
Pipeline
Production
compilation unit tests
linting integration tests
business metrics
customer feedbackincidents
technical metricsperformance tests
security scanning

Culture
Pipeline
10
Testing
Tooling
Development Deployment

Culture
Pipeline
11
Testing
Tooling
Development Deployment

12
Sensible default #2:
Trunk-based
development
🌴

Culture
Pipeline
14
Testing
Tooling
Development Deployment

15
Com
pile
Lint
U
nittest
Contracttest
Integration
test
Static
analysis
Journey
test
CFR
tests
D
eploy
to
pre-prod
Sm
oke
testD
eploy
to
prod
Sm
oke
test
D
ependency
license
check
D
ependency 
vulnerability 
check
D
ependency 
update 
check
Image credit: https://martinfowler.com/bliki/TestPyramid.html
Com
m
it

16
Sensible default #4:
The pipeline is the 
only way
$

17
Sensible default #5:
Decoupled pipelines
⛓

18
Sensible default #6:
Build once,  
use everywhere
☝

19
Sensible default #7:
Two (or three)
environments
🏭

Culture
Pipeline
20
Testing
Tooling
Development Deployment

21
Sensible default #8:
Deployment ≠ release
🎉

22
Sensible default #9:
Automated  
deployments
🤖

23
Sensible default #1:
Continuous 
Deployment
✨

24
Sensible default #10:
Zero-downtime
deployments
⏱

25
Sensible default #11:
Gradual 
deployments
🦜

26
Sensible default #12:
Verified 
deployments
🦜
💨

Culture
Pipeline
28
Testing
Tooling
Development Deployment

29
Sensible default #14:
Always be testing
🔬

30
Sensible default #15:
CFRs in pipeline
🔨

31
Sensible default #16:
Automated, repeatable,
isolated tests
⚙

Culture
Pipeline
32
Testing
Tooling
Development Deployment

33
Sensible default #17:
The pipeline is not
special
🎲

34
Sensible default #18:
Automated  
compliance
📋

35
Sensible default #19:
Pipeline is code
📜

36
Sensible default #20:
Config is code
📚

37
Sensible default #21:
Logging, monitoring 
and alerting owned by
dev team
🚨

38
Sensible default #22:
Synthetic monitoring
🧐

Culture
Pipeline
39
Testing
Tooling
Development Deployment

40
Sensible default #23:
You build it, you run it 
(it breaks, you wake)
🛌

Culture
Pipeline
41
Testing
Tooling
Development Deployment

Establish Continuous Deployment as goal 
and work backwards
43

44
Sensible default #24:
Paved roads and  
building blocks
🛣

46
Logging,
monitoring and
alerting owned
by dev team
Zero-downtime
deployments
Two (or three)
environments
Continuous
Deployment
Decoupled
pipelines
Build once,  
use everywhere
The pipeline is
not special
Synthetic
monitoring
Always be testing
Automated,
repeatable,
isolated tests
Pairing
The pipeline is
the only way
Roll forward
Gradual
deployments
Config is code
You build it,  
you run it
Automated
deployments
Paved roads and
building blocks
Trunk-based
development
CFRs in pipeline
Deployment  
≠ release
Pipeline is code
Automated
compliance
Verified
deployments

Similar to Sensible defaults for CI and CD in 2019

In mission- and safety-critical industries, static code analysis (SCA) is key to facilitating the development of robust and reliable software - yet, according to VDC Research, only 27% of embedded developers report using SCA tools on their current project. Why is adoption low and what can you do to deploy SCA effectively? Join Walter Capitani (Rogue Wave Software) and Christopher Rommel (VDC Research) as they review the results of the latest VDC Research paper on the trends, techniques, and best practices for standards compliance within embedded software teams. You will learn what organizations like yours are doing now and how to prepare for future challenges by: -Understanding trends for standards compliance in 2018 -Identifying common challenges for automotive, medical, industrial automation, and other types of applications -Learning best practices for achieving compliance using different tools, techniques, and processes After attending this webinar, you'll be better prepared to plan and execute a standards compliance program for your team and maximize the effectiveness of static code analysis.

5 Ways to Accelerate Standards Compliance with Static Code Analysis

Perforce

Jenkins is one of the most popular tools for Continuous Integration and Continuous Delivery today. It’s easy to set up and get started with. But what are the best practices for building delivery pipelines with Jenkins? Should you use the traditional build jobs or opt for the new Jenkins pipelines? What options are there for, e.g. visualization or infrastructure as code support? How do I structure my shared libraries so that they’re easy to maintain? In this talk, I’ll share my many years of experiences from working with Jenkins for Continuous Delivery. We’ll take a look at pros and cons of different approaches but also how Jenkins compares to its competitors, where it shines, and where it leaves room for improvement. Presented at JAX DevOps & Finance, London, United Kingdom on April 10th 2018.

Continuous Delivery with Jenkins: the Good, the Bad and the Ugly - JAX DevOps...

Tommy Tynjä

Finding the important bugs- A talk by John Scarborough, Director of Testing, ...

HARMAN Services

CI/CD for React Native

Joao Marins

Intsoc2

jogajosh

If you want to discover answers for the most often asked questions as below, glance through this presentation - Questions often asked - Do we get timely build with Quality? Do we know/have capability matrix of the team? Do we have resource/head count utilization charts? Are we sure if features are validated on time? Do we know if engineers understand what customers are expecting? Do we have right channel of prioritization? Do we have right change management control in place? Do we know if we have tested enough?

Building products - A Nifty Approach

GuruprasadBhat21

Dan Sturtevant, Silverthread and Niles Madison at Synopsys discussed design quality and code quality on a recent webinar. In an acquisition where a software asset is a core part of the deal valuation, it’s important to understand the overall quality of the software prior to doing the deal. Buggy software is problematic and needs to be cleaned up, so assessing code quality is important. But also, with poorly designed software, every fix is costly and laborious. This can significantly impact the long-term viability of the application, and maintaining that software can seriously degrade ROI. That’s why understanding a software system’s design or architectural health and the likely 'cost of ownership' is key.. For more information, please visit our website at https://www.synopsys.com/open-source-audit

Do Design Quality and Code Quality Matter in Merger and Acquisition Tech Due ...

Synopsys Software Integrity Group

DevOps with OpenShift - Fabien Dupont - ManageIQ Design Summit 2016

ManageIQ

Old staging methodology is broken for modern development. In fact, the staging server is left over from when we built monolithic applications. Find out why microservice architectures are driving ephemeral testing environments & why every sized dev shop should deliver true continuous deployment. Staging servers slow down development with merge conflicts, slow iteration loops, and manhour intensive processes. To build better software faster containers and infrastructure as code are key in 2017. Dev Ops professionals miss this talk at their own peril.

Why You Need to Stop Using "The" Staging Server

Outlyer

Integrating Black Duck into your Agile DevOps Environment

Black Duck by Synopsys

Kim Carter (BinaryMist)

AgileNZ Conference

In this talk, we will cover important elements for successful CI and CD. We will discuss how these elements make CI and CD much simpler, and hence more attainable. We will cover some best practices / recommendations to include in your application pipelines. We will look at a sample implementation of a pipeline leveraging modern tools. Finally, we will discuss some forthcoming ideas for making it even easier to declaratively enable CI and CD for applications.

Delivery Pipelines as a First Class Citizen @deliverAgile2019

ciberkleid

In 2015, the Standard & Poor’s Ratings IT team set out an ambitious objective—to tighten the process and controls around the quality of code deployed to production. Based on internal cost of quality assessments, and supporting agile and waterfall internal engineering processes, distinct testing levels were identified to help push quality left and root out the underlying causes of defects as early as possible. The ‘14 Levels of Testing’ were defined to collaboratively span organizational functions, establish quality expectations, and help track towards the goal of eliminating defects. Adrian Thibodeau and Chintan Pandya review their 14 Levels of Testing and focus specifically on sharing the processes and tools employed to help govern the delivery of quality. Adrian and Chintan discuss metrics and dashboards, defect lifecycle management, their home-grown QA Workflow Portal, testing vendor SLAs and contracts, and facilitating UAT best-practices.

End-to-End Quality Approach: 14 Levels of Testing

Josiah Renaudin

MOPCON 2015 - Tips of Mobile Continuous Delivery

anistar sung

Components of CI/CD in DevOps

sunil173422

Sandia blade reliability conf

Vince Foody

Your IT department supports critical business functions, processes and pDevOps promises high velocity in lean software development, where delivery is frequent with minimal manual intervention in a highly collaborative environment. The outcome is to delight the customer quickly and frequently! However, this is far from reality as practitioners are often forced to align with the business in an environment that is increasingly fragmented with many isolated and complex solutions. Whist user stories are there to deliver outcomes, many organisations lack visibility of how the delivery lifecycle directly impacts business goals like user signups, cart fulfillment, customer satisfaction, social sentiment, or revenue. Consequently, the customer still has a poor experience – how things are delivered are as important as what is delivered.

The DevOps Promise: Helping Management Realise the Quality, Velocity & Effici...

Splunk

CI/CD Pipeline mit Gitlab CI und Kubernetes

inovex GmbH

Using Apache Spark for Predicting Degrading and Failing Parts in Aviation

Databricks

In this webinar, learn how an open toolchain (including Git, SonarQube, IBM UrbanCode Deploy, and IBM Dependency Based Build) is key to driving a modern pipeline. Experts Rosalind Radcliffe and Suman Gopinath will demonstrate where traditional z/OS applications can fit in an existing modern toolchain with minimal modifications. Your developers can use the same tools and practices, but without the pain and effort of a host-based solution that currently limits their ability. This webinar will show how a modern pipeline can break down silos and reduce costs, with minimal additions to your current pipeline.

Replace Outdated DevOps Tools with Innovative & Modern Pipelines

DevOps.com

Similar to Sensible defaults for CI and CD in 2019 (20)

5 Ways to Accelerate Standards Compliance with Static Code Analysis

Continuous Delivery with Jenkins: the Good, the Bad and the Ugly - JAX DevOps...

Finding the important bugs- A talk by John Scarborough, Director of Testing, ...

CI/CD for React Native

Intsoc2

Building products - A Nifty Approach

Do Design Quality and Code Quality Matter in Merger and Acquisition Tech Due ...

DevOps with OpenShift - Fabien Dupont - ManageIQ Design Summit 2016

Why You Need to Stop Using "The" Staging Server

Integrating Black Duck into your Agile DevOps Environment

Kim Carter (BinaryMist)

Delivery Pipelines as a First Class Citizen @deliverAgile2019

End-to-End Quality Approach: 14 Levels of Testing

MOPCON 2015 - Tips of Mobile Continuous Delivery

Components of CI/CD in DevOps

Sandia blade reliability conf

The DevOps Promise: Helping Management Realise the Quality, Velocity & Effici...

CI/CD Pipeline mit Gitlab CI und Kubernetes

Using Apache Spark for Predicting Degrading and Failing Parts in Aviation

Replace Outdated DevOps Tools with Innovative & Modern Pipelines

More from Thoughtworks

Design System as a Product - Maria Elena Duenias, Esther Butcher Design systems are a great example where web development and design meet. You can find innumerable resources on the internet, books and conferences on how to build them, and how they are exactly what your organization needs. But, building one requires a lot more than following a recipe. In this talk we are going to discuss how to build a design system as an internal product, and how it evolves to become what the users need.

Design System as a Product

Thoughtworks

Designers, Developers and Dogs: Finding the magic balance between product and tech - Charlotte Vorbeck, ShareNow and Sahil Bajaj How can an agile delivery team become a successful product team? When does collaboration between product and tech succeed and when not? Why do people in some teams inspire each other while others in the same environment don't speak the same language? In this talk we want to share our learnings and experiences from rebuilding an internal tool for customer support at ShareNow. What could have been just another boring rewrite surprisingly became one of our best experiences in collaboration. We will look at how a joint discovery phase helped us to come up with a shared vision, how a better team setup enabled us to do the necessary work, how focusing on the customer kept us aligned during our journey, and also how we built upon existing collaborative techniques to achieve this new level of cooperation and trust.

Designers, Developers & Dogs

Thoughtworks

Cloud-first for fast innovation

Thoughtworks

How to create more business impact with flexible teams - Jan Hegewald, Zalando & Rebekka Beels, Zalando Usually, Software Engineering teams are organized around a fixed set of components which they develop further and maintain. Such component teams gain a high level of expert knowledge about their services. However, with agile product development, it often is difficult to implement the most important initiatives with such teams. This leads to a situation where the teams do not work on the most relevant business topics but on those for the respective team. At Zalando, we introduced a new model where we shape teams flexibly around business goals to create the highest impact. How we organize these teams and which challenges especially for the software quality need to be addressed, will be explored in this talk.

More impact with flexible teams

Thoughtworks

Culture of Innovation

Thoughtworks

Dual-Track Agile for Discovery & Development - Adriana Katrandzhieva The talk will focus on one of the ways teams can ensure continuous delivery and design in their projects. The so-called ‘Dual-track’ model shows the parallel tracks of discovery and development throughout the product design and delivery process. These continually feedback into each other informing new hypothesis that can be tested in order to be proven/disproven. This model is not always easy to implement out of the box and so I will share my own experiences in applying it in practice - what worked, what didn't and how the model can be adjusted to fit different teams and organisational environments.

Dual-Track Agile

Thoughtworks

Designing the Developer Experience - Tanja Bach, Jacob Bo Tiedemann Working with software that some other people have built, is not only daily business for private and business users but also for developers. Just like any other product, a product for developers needs to solve their problems and focus on the right jobs-to-be-done in order to be successfully adopted by the developer community. In this talk, we will explain why the developer experience matters not only to developers but also to the business. We will share our learnings and real-world examples of how we created a developer experience for a cloud infrastructure product and an IoT platform that the developers love.

Developer Experience

Thoughtworks

When we design together - Sabrina Mach, Ammara Gafoor and James Emmott From three distinct perspectives, this talk will contend that design is an activity undertaken by everyone in a software development team. It occurs throughout the process of delivery — not only at the beginning or the end — and it is a powerful instrument for learning about and adapting to the problems our work seeks to solve, which is a shared responsibility. Making the best use of our multidisciplinary expertise in the activity of design requires forms of collaboration that are too often disrupted by the role-based silos that keep us separated and weaken the valuable contribution our diverse approaches could make to our collective efforts. If you care about accelerating time to market, improving customer experience, or building happy and productive teams, you will want to know why and how it matters that we believe ‘design is in everything that we do’.

When we design together

Thoughtworks

Hardware is hard(er): designing for distributed user experiences in IoT - Claire Rowland, www.clairerowland.com Designing connected devices and hardware-enabled services is significantly more complex than pure software. There are more devices on which code can run, connectivity and data sharing patterns to consider, and often multiple and varied touchpoints for users to interact with. Pulling this all together into a coherent experience involves strong collaboration between design and engineering, and a systems thinking approach to UX. In this talk, we’ll introduce what designers need to know about the tech, what engineers need to know about UX for IoT, and how to facilitate the whole-collaboration needed to create great products. www.clairerowland.com

Hardware is hard(er)

Thoughtworks

Customer-centric innovation enabled by cloud

Thoughtworks

Amazon's Culture of Innovation

Thoughtworks

Find out how to validate hypotheses quickly using feedback that comes from a (large enough) number of actual users interacting with your product. In this talk, we will show you the technical foundations, research techniques and organisational setup that we have used successfully on large-scale products. These will save you development time, enable you to go live with confidence, make decisions based on real behaviour instead of best guesses, and solve the actual problems your users are facing.

When in doubt, go live

Thoughtworks

As a tech leader at ThoughtWorks, a large part of my job involves recommending practices to our clients so they can build and deliver good quality software faster. In doing so repeatedly for many clients I have created a toolkit that contains practical advice from being on the ground. This is what we do, we know it works. When Julius Caesar entered Rome with his army by crossing the river Rubicon, he did something that couldn’t be undone ever again. In your journey as a leader, avoid mistakes that are difficult to correct later. Here are a set of practices that you want to adopt as soon as possible.

Don't cross the Rubicon

Thoughtworks

Handling error conditions is a core part of the software we write. However, we often treat it as a second class citizen, obscuring our intent through abuse of null values and exceptions that make our code hard to understand and maintain. In the functional programming community, it is common to use datatypes such as Option, Either or Validated to make our intentions explicit when dealing with errors. We can leverage the compiler to verify that we are handling them instead of hoping for the best at runtime. This results in code that is clearer, without hidden path flows. We’ll show how we have been doing this in Kotlin, with the help of the Arrow library.

Error handling

Thoughtworks

Your test coverage is a lie!

Thoughtworks

Docker container security

Thoughtworks

Mainframes handle 30 billion business transactions each day and 87% of all credit card transactions*, they are not traditionally associated with flexible, fail-fast development approaches. Can we bring the practices of agile, CI/CD and fully automated deployments to applications running on a mainframe? During our talk, we'll tell you a story about test automation; redefining the smallest testable unit of a program. And we'll discuss our learnings from introducing continuous integration and agile practices to the world of insurance and mainframes. *9 Mainframe statistics that may surprise you

Redefining the unit

Thoughtworks

Technology Radar Webinar UK - Vol. 22

Thoughtworks

A Tribute to Turing

Thoughtworks

Rsa maths worked out

Thoughtworks

More from Thoughtworks (20)

Design System as a Product

Designers, Developers & Dogs

Cloud-first for fast innovation

More impact with flexible teams

Culture of Innovation

Dual-Track Agile

Developer Experience

When we design together

Hardware is hard(er)

Customer-centric innovation enabled by cloud

Amazon's Culture of Innovation

When in doubt, go live

Don't cross the Rubicon

Error handling

Your test coverage is a lie!

Docker container security

Redefining the unit

Technology Radar Webinar UK - Vol. 22

A Tribute to Turing

Rsa maths worked out

Recently uploaded

Real Time Object Detection Using Open CV

Khem

Following the popularity of "Cloud Revolution: Exploring the New Wave of Serverless Spatial Data," we're thrilled to announce this much-anticipated encore webinar. In this sequel, we'll dive deeper into the Cloud-Native realm by uncovering practical applications and FME support for these new formats, including COGs, COPC, FlatGeoBuf, GeoParquet, STAC, and ZARR. Building on the foundation laid by industry leaders Michelle Roby of Radiant Earth and Chris Holmes of Planet in the first webinar, this second part offers an in-depth look at the real-world application and behind-the-scenes dynamics of these cutting-edge formats. We will spotlight specific use-cases and workflows, showcasing their efficiency and relevance in practical scenarios. Discover the vast possibilities each format holds, highlighted through detailed discussions and demonstrations. Our expert speakers will dissect the key aspects and provide critical takeaways for effective use, ensuring attendees leave with a thorough understanding of how to apply these formats in their own projects. Elevate your understanding of how FME supports these cutting-edge technologies, enhancing your ability to manage, share, and analyze spatial data. Whether you're building on knowledge from our initial session or are new to the serverless spatial data landscape, this webinar is your gateway to mastering cloud-native formats in your workflows.

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Safe Software

MySQL Webinar, presented on the 25th of April, 2024. Summary: MySQL solutions enable the deployment of diverse Database Architectures tailored to specific needs, including High Availability, Disaster Recovery, and Read Scale-Out. With MySQL Shell's AdminAPI, administrators can seamlessly set up, manage, and monitor these solutions, ensuring efficiency and ease of use in their administration. MySQL Router, on the other hand, provides transparent routing from the application traffic to the backend servers in the architectures, requiring minimal configuration. Completely built in-house and supported by Oracle, these solutions have been adopted by enterprises of all sizes for their business-critical applications. In this presentation, we'll delve into various database architecture solutions to help you choose the right one based on your business requirements. Focusing on technical details and the latest features to maximize the potential of these solutions.

Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...

Miguel Araújo

This presentations targets students or working professionals. You may know Google for search, YouTube, Android, Chrome, and Gmail, but did you know Google has many developer tools, platforms & APIs? This comprehensive yet still high-level overview outlines the most impactful tools for where to run your code, store & analyze your data. It will also inspire you as to what's possible. This talk is 50 minutes in length.

Powerful Google developer tools for immediate impact! (2023-24 C)

wesley chun

AXA XL - Insurer Innovation Award Americas 2024

The Digital Insurer

Abhishek Deb(1), Mr Abdul Kalam(2) M. Des (UX) , School of Design, DIT University , Dehradun. This paper explores the future potential of AI-enabled smartphone processors, aiming to investigate the advancements, capabilities, and implications of integrating artificial intelligence (AI) into smartphone technology. The research study goals consist of evaluating the development of AI in mobile phone processors, analyzing the existing state as well as abilities of AI-enabled cpus determining future patterns as well as chances together with reviewing obstacles as well as factors to consider for more growth.

Exploring the Future Potential of AI-Enabled Smartphone Processors

debabhi2

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

Juan lago vázquez

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

ICT role in 21st century education and its challenges

rafiqahmad00786416

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

MINDCTI Revenue Release Quarter One 2024

MIND CTI

Boost Fertility New Invention Ups Success Rates.pdf

sudhanshuwaghmare1

FWD Group - Insurer Innovation Award 2024

The Digital Insurer

Scaling API-first – The story of a global engineering organization Ian Reasor, Senior Computer Scientist - Adobe Radu Cotescu, Senior Computer Scientist - Adobe Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

apidays

The Good, the Bad and the Governed - Why is governance a dirty word? David O'Neill, Chief Operating Officer - APIContext Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

apidays

The value of a flexible API Management solution for Open Banking Steve Melan, Manager for IT Innovation and Architecture - State's and Saving's Bank of Luxembourg Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The value of a flexible API Management solution for O...

apidays

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

MadyBayot

Recently uploaded (20)

Real Time Object Detection Using Open CV

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME

Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...

Powerful Google developer tools for immediate impact! (2023-24 C)

AXA XL - Insurer Innovation Award Americas 2024

Exploring the Future Potential of AI-Enabled Smartphone Processors

AWS Community Day CPH - Three problems of Terraform

Polkadot JAM Slides - Token2049 - By Dr. Gavin Wood

2024: Domino Containers - The Next Step. News from the Domino Container commu...

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Axa Assurance Maroc - Insurer Innovation Award 2024

ICT role in 21st century education and its challenges

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

MINDCTI Revenue Release Quarter One 2024

Boost Fertility New Invention Ups Success Rates.pdf

FWD Group - Insurer Innovation Award 2024

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

Apidays New York 2024 - The value of a flexible API Management solution for O...

EMPOWERMENT TECHNOLOGY GRADE 11 QUARTER 2 REVIEWER

Sensible defaults for CI and CD in 2019

1. 1 1 SENSIBLE DEFAULTS FOR CI/CD IN 2019 Charles Korn

2. Ready to make your mark? /careers

3. Sensible defaults for CI/CD in 2019 Charles Korn

4. 👋 4

5. Some assumptions 5

6. 6 Mean time   to recovery Deployment frequency Lead time   to change Change   failure rate

7. 7 Time Seconds Minutes Hours Days Weeks Dev working locally Pipeline Production compilation unit tests linting integration tests business metrics customer feedbackincidents technical metricsperformance tests security scanning

8. 8 Image credit: mindgamesbrisbane.com

9. Sensible default? 9

10. Culture Pipeline 10 Testing Tooling Development Deployment

11. Culture Pipeline 11 Testing Tooling Development Deployment

12. 12 Sensible default #2: Trunk-based development 🌴

13. 13 Sensible default #3: Pairing 🍐

14. Culture Pipeline 14 Testing Tooling Development Deployment

15. 15 Com pile Lint U nittest Contracttest Integration test Static analysis Journey test CFR tests D eploy to pre-prod Sm oke testD eploy to prod Sm oke test D ependency license check D ependency  vulnerability  check D ependency  update  check Image credit: https://martinfowler.com/bliki/TestPyramid.html Com m it

16. 16 Sensible default #4: The pipeline is the  only way $

17. 17 Sensible default #5: Decoupled pipelines ⛓

18. 18 Sensible default #6: Build once,   use everywhere ☝

19. 19 Sensible default #7: Two (or three) environments 🏭

20. Culture Pipeline 20 Testing Tooling Development Deployment

21. 21 Sensible default #8: Deployment ≠ release 🎉

22. 22 Sensible default #9: Automated   deployments 🤖

23. 23 Sensible default #1: Continuous  Deployment ✨

24. 24 Sensible default #10: Zero-downtime deployments ⏱

25. 25 Sensible default #11: Gradual  deployments 🦜

26. 26 Sensible default #12: Verified  deployments 🦜 💨

27. 27 Sensible default #13: Roll forward ➡

28. Culture Pipeline 28 Testing Tooling Development Deployment

29. 29 Sensible default #14: Always be testing 🔬

30. 30 Sensible default #15: CFRs in pipeline 🔨

31. 31 Sensible default #16: Automated, repeatable, isolated tests ⚙

32. Culture Pipeline 32 Testing Tooling Development Deployment

33. 33 Sensible default #17: The pipeline is not special 🎲

34. 34 Sensible default #18: Automated   compliance 📋

35. 35 Sensible default #19: Pipeline is code 📜

36. 36 Sensible default #20: Config is code 📚

37. 37 Sensible default #21: Logging, monitoring  and alerting owned by dev team 🚨

38. 38 Sensible default #22: Synthetic monitoring 🧐

39. Culture Pipeline 39 Testing Tooling Development Deployment

40. 40 Sensible default #23: You build it, you run it  (it breaks, you wake) 🛌

41. Culture Pipeline 41 Testing Tooling Development Deployment

42. How can I make this happen? 42

43. Establish Continuous Deployment as goal  and work backwards 43

44. 44 Sensible default #24: Paved roads and   building blocks 🛣

45. Recap 45

46. 46 Logging, monitoring and alerting owned by dev team Zero-downtime deployments Two (or three) environments Continuous Deployment Decoupled pipelines Build once,   use everywhere The pipeline is not special Synthetic monitoring Always be testing Automated, repeatable, isolated tests Pairing The pipeline is the only way Roll forward Gradual deployments Config is code You build it,   you run it Automated deployments Paved roads and building blocks Trunk-based development CFRs in pipeline Deployment   ≠ release Pipeline is code Automated compliance Verified deployments

47. 47

Sensible defaults for CI and CD in 2019

Recommended

Recommended

More Related Content

Similar to Sensible defaults for CI and CD in 2019

Similar to Sensible defaults for CI and CD in 2019 (20)

More from Thoughtworks

More from Thoughtworks (20)

Recently uploaded

Recently uploaded (20)

Sensible defaults for CI and CD in 2019