SlideShare a Scribd company logo
1 of 27
Introduction to CI/CD
Steve Mactaggart
State Manager - Victoria
Agenda
● What is CI and CD
● What makes good CI / CD
● How we get there
● Business benefits of it all….
What is CI and CD?
● Continuous Integration
○ An approach to be continually validating the state of a codebase
through automated testing.
○ Best achieved through integration with version control
● Continuous Delivery / Deployment
○ An approach to regularly deploying artifacts that successfully pass
the CI phase to ensure confidence around the deployment
Delivery vs Deployment
Continuous integration, continuous deployment,
and continuous delivery are like vectors that have the same
direction, but different magnitude.
Their goal is the same: make our software development and
release process faster and more robust.
The key difference between the three is in the scope of
automation applied.
Delivery vs Deployment
● Continuous Delivery
○ Automatically prepare and track a release to production
○ The desired outcome is that anyone with sufficient privileges to deploy a new
release can do so at any time in one or a few clicks. By eliminating nearly all
manual tasks, developers become more productive.
● Continuous Deployment
○ Every change in the source code is deployed to production automatically,
without explicit approval from a developer.
○ As long as it passes the quality controls
What does good look like?
What makes for good CI?
1. Decoupled stages
○ Each step in CI should do a single focused task
2. Repeatable
○ Automated in a way that is consistently repeatable
○ Tooling should work for local developers too – Local/Remote parity
3. Fail fast
○ Fail at the first sign of trouble
The test pyramid
https://martinfowler.com/bliki/TestPyramid.html
What makes for good CD?
1. Design with the system in mind
○ Cover as many parts of a deployment as possible
○ Application | Infrastructure | Configuration | Data
2. Pipelines
○ Continually increase confidence as you move towards production
3. Globally unique versions
○ Know the state of the system at any time
○ Be able to demonstrate difference between current and future state
CD Pipeline flow
DEV PRE PROD PRODUCTIONConfiguration
Infrastructure
Application
Bringing CI & CD together
Continuous
Integration
Knowing the artifacts
are Good
Knowing the
deployment is Good
Continuous
Delivery /
Deployment
Artifact
store
Full deployment pipeline
https://www.oreilly.com/learning/configuring-a-continuous-delivery-pipeline-in-jenkins
Tracking Confidence
Where do we start?
How do we know we are progressing?
1. Assess the current state
2. WSJF
3. Think globally – act locally
○ Proof of Concept and Spikes are your friends
1. Assess the current state
2. WSJF
3. Think globally – act locally
○ Proof of Concept and Spikes are your friends
Unit testing and shifting left
● Make the tests easy to run
○ Run them locally
■ Invest in good quality IDE support
○ Consistent entrypoint - Abstract the complexity
■ Makefiles / Gradle
○ Pull request unit test execution
Failing fast
● Code inspection
○ Code linting
○ Security inspection
○ Code format
● Code coverage
○ Track coverage changes
Centralised artifacts
● Managing output from a CI process
○ Only the strong survive
○ Central common location
○ Clearly understood name and version approach
○ Build them only once
○ Make them timeless – externalise configuration
Business benefits of CI/CD
Why do this?
● Reduction of delivery risk
○ No longer do we need to rely on humans with specific knowledge as
the gate-keepers of quality
○ Reduced chance of humans not following the process
○ Reduced chance of mis-communication on executing the change
Why do this?
● To encode the process, we need to know the process
○ If we know all the tests pass,
○ If we know all the steps in deployment,
○ What is stopping us from releasing?
Why do this?
● Better visibility on change
○ As our systems and tools are version controlled
○ And we know what the current state of production is
○ And we can describe the process by which it will be changed
○ We can diff the system states with confidence
● Opens up more avenues for review and increased audit
compliance
Why do this?
● Increased efficiency and delivery options
○ Enables us to deliver things with reduced effort
○ This leads us to deploy change more frequently
○ Which leads to getting feedback faster
○ That enables us to experiment easier
○ This leads to smaller batch sizes
○ Which leads to and increased flow of the entire system
Why do this?
● Enhanced learning from failure
○ When we have an issue or failure, we write a test to cover it
○ This test gets added to our suite and executed every time
○ Decreases our risk of this issue occurring again
That’s all folks…
Steve Mactaggart
State Manager – Victoria
steve.mactaggart@cevo.com.au

More Related Content

What's hot

DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...
DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...
DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...
Simplilearn
 
Continuous integration
Continuous integrationContinuous integration
Continuous integration
amscanne
 

What's hot (20)

Introduction to DevOps
Introduction to DevOpsIntroduction to DevOps
Introduction to DevOps
 
Fundamentals of DevOps and CI/CD
Fundamentals of DevOps and CI/CDFundamentals of DevOps and CI/CD
Fundamentals of DevOps and CI/CD
 
CICD with Jenkins
CICD with JenkinsCICD with Jenkins
CICD with Jenkins
 
Build CICD Pipeline for Container Presentation Slides
Build CICD Pipeline for Container Presentation SlidesBuild CICD Pipeline for Container Presentation Slides
Build CICD Pipeline for Container Presentation Slides
 
Gitlab CI/CD
Gitlab CI/CDGitlab CI/CD
Gitlab CI/CD
 
DevOps for beginners
DevOps for beginnersDevOps for beginners
DevOps for beginners
 
Introduction to kubernetes
Introduction to kubernetesIntroduction to kubernetes
Introduction to kubernetes
 
Transforming Organizations with CI/CD
Transforming Organizations with CI/CDTransforming Organizations with CI/CD
Transforming Organizations with CI/CD
 
DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...
DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...
DevOps Tutorial For Beginners | DevOps Tutorial | DevOps Tools | DevOps Train...
 
Modern CI/CD Pipeline Using Azure DevOps
Modern CI/CD Pipeline Using Azure DevOpsModern CI/CD Pipeline Using Azure DevOps
Modern CI/CD Pipeline Using Azure DevOps
 
An introduction to DevOps
An introduction to DevOpsAn introduction to DevOps
An introduction to DevOps
 
Building a CICD pipeline for deploying to containers
Building a CICD pipeline for deploying to containersBuilding a CICD pipeline for deploying to containers
Building a CICD pipeline for deploying to containers
 
Jenkins Overview
Jenkins OverviewJenkins Overview
Jenkins Overview
 
What is Jenkins | Jenkins Tutorial for Beginners | Edureka
What is Jenkins | Jenkins Tutorial for Beginners | EdurekaWhat is Jenkins | Jenkins Tutorial for Beginners | Edureka
What is Jenkins | Jenkins Tutorial for Beginners | Edureka
 
Continuous integration
Continuous integrationContinuous integration
Continuous integration
 
Introduction to DevOps
Introduction to DevOpsIntroduction to DevOps
Introduction to DevOps
 
CI and CD with Jenkins
CI and CD with JenkinsCI and CD with Jenkins
CI and CD with Jenkins
 
Dev ops != Dev+Ops
Dev ops != Dev+OpsDev ops != Dev+Ops
Dev ops != Dev+Ops
 
An Introduction To Jenkins
An Introduction To JenkinsAn Introduction To Jenkins
An Introduction To Jenkins
 
Gitlab ci-cd
Gitlab ci-cdGitlab ci-cd
Gitlab ci-cd
 

Similar to Introduction to CI/CD

DevOps/Flow workshop for agile india 2015
DevOps/Flow workshop for agile india 2015DevOps/Flow workshop for agile india 2015
DevOps/Flow workshop for agile india 2015
Yuval Yeret
 

Similar to Introduction to CI/CD (20)

Developing Quality Products Quickly through a Culture of CI/CD
Developing Quality Products Quickly through a Culture of CI/CDDeveloping Quality Products Quickly through a Culture of CI/CD
Developing Quality Products Quickly through a Culture of CI/CD
 
Continues delivery - Introduction
Continues delivery - IntroductionContinues delivery - Introduction
Continues delivery - Introduction
 
Testing in a continuous delivery environment
Testing in a continuous delivery environmentTesting in a continuous delivery environment
Testing in a continuous delivery environment
 
Software Release Orchestration and the Enterprise
Software Release Orchestration and the EnterpriseSoftware Release Orchestration and the Enterprise
Software Release Orchestration and the Enterprise
 
2019 State of DevOps Report: Database Best Practices for Strong DevOps
2019 State of DevOps Report: Database Best Practices for Strong DevOps2019 State of DevOps Report: Database Best Practices for Strong DevOps
2019 State of DevOps Report: Database Best Practices for Strong DevOps
 
Measure and Accelerate Your Software Delivery
Measure and Accelerate Your Software DeliveryMeasure and Accelerate Your Software Delivery
Measure and Accelerate Your Software Delivery
 
Software Quality for Developers
Software Quality for DevelopersSoftware Quality for Developers
Software Quality for Developers
 
San Francisco Jenkins Area Meetup October 2016: Self-service secure test and ...
San Francisco Jenkins Area Meetup October 2016: Self-service secure test and ...San Francisco Jenkins Area Meetup October 2016: Self-service secure test and ...
San Francisco Jenkins Area Meetup October 2016: Self-service secure test and ...
 
DevTestOps
DevTestOpsDevTestOps
DevTestOps
 
The Continuous Delivery process
The Continuous Delivery processThe Continuous Delivery process
The Continuous Delivery process
 
Continuous Delivery Distilled
Continuous Delivery DistilledContinuous Delivery Distilled
Continuous Delivery Distilled
 
Continuous Delivery: why ? where to start ? how to scale ?
Continuous Delivery: why ? where to start ? how to scale ?Continuous Delivery: why ? where to start ? how to scale ?
Continuous Delivery: why ? where to start ? how to scale ?
 
The Final Frontier, Automating Dynamic Security Testing
The Final Frontier, Automating Dynamic Security TestingThe Final Frontier, Automating Dynamic Security Testing
The Final Frontier, Automating Dynamic Security Testing
 
Continuously delivering software to big brands (fullscreen edition)
Continuously delivering software to big brands (fullscreen edition)Continuously delivering software to big brands (fullscreen edition)
Continuously delivering software to big brands (fullscreen edition)
 
6 Tools for Improving IT Operations in ICS Environments
6 Tools for Improving IT Operations in ICS Environments6 Tools for Improving IT Operations in ICS Environments
6 Tools for Improving IT Operations in ICS Environments
 
DevOps/Flow workshop for agile india 2015
DevOps/Flow workshop for agile india 2015DevOps/Flow workshop for agile india 2015
DevOps/Flow workshop for agile india 2015
 
Data Engineer's Lunch #68: DevOps Fundamentals
Data Engineer's Lunch #68: DevOps FundamentalsData Engineer's Lunch #68: DevOps Fundamentals
Data Engineer's Lunch #68: DevOps Fundamentals
 
The Continuous delivery value - Funaro
The Continuous delivery value - FunaroThe Continuous delivery value - Funaro
The Continuous delivery value - Funaro
 
The Continuous delivery Value @ codemotion 2014
The Continuous delivery Value @ codemotion 2014The Continuous delivery Value @ codemotion 2014
The Continuous delivery Value @ codemotion 2014
 
HIS 2017 Paul Sherwood- towards trustable software
HIS 2017 Paul Sherwood- towards trustable software HIS 2017 Paul Sherwood- towards trustable software
HIS 2017 Paul Sherwood- towards trustable software
 

More from Steve Mactaggart

More from Steve Mactaggart (6)

5 DevOps things that have changed because of COVID-19
5 DevOps things that have changed because of COVID-195 DevOps things that have changed because of COVID-19
5 DevOps things that have changed because of COVID-19
 
Are you a leadership group or a leadership team?
Are you a leadership group or a leadership team?Are you a leadership group or a leadership team?
Are you a leadership group or a leadership team?
 
Test driven infrastructure
Test driven infrastructureTest driven infrastructure
Test driven infrastructure
 
Jenkins as a Service - Code all the way down
Jenkins as a Service - Code all the way downJenkins as a Service - Code all the way down
Jenkins as a Service - Code all the way down
 
The changing role of the team leader in a DevOps transformation
The changing role of the team leader in a DevOps transformationThe changing role of the team leader in a DevOps transformation
The changing role of the team leader in a DevOps transformation
 
Head in the clouds
Head in the cloudsHead in the clouds
Head in the clouds
 

Recently uploaded

Why Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire businessWhy Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire business
panagenda
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Safe Software
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
WSO2
 

Recently uploaded (20)

Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...
Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...
Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...
 
Why Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire businessWhy Teams call analytics are critical to your entire business
Why Teams call analytics are critical to your entire business
 
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdfRising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf
 
Elevate Developer Efficiency & build GenAI Application with Amazon Q​
Elevate Developer Efficiency & build GenAI Application with Amazon Q​Elevate Developer Efficiency & build GenAI Application with Amazon Q​
Elevate Developer Efficiency & build GenAI Application with Amazon Q​
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
 
Architecting Cloud Native Applications
Architecting Cloud Native ApplicationsArchitecting Cloud Native Applications
Architecting Cloud Native Applications
 
Strategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a FresherStrategies for Landing an Oracle DBA Job as a Fresher
Strategies for Landing an Oracle DBA Job as a Fresher
 
Boost Fertility New Invention Ups Success Rates.pdf
Boost Fertility New Invention Ups Success Rates.pdfBoost Fertility New Invention Ups Success Rates.pdf
Boost Fertility New Invention Ups Success Rates.pdf
 
Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...Apidays New York 2024 - The value of a flexible API Management solution for O...
Apidays New York 2024 - The value of a flexible API Management solution for O...
 
AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 
Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)Introduction to Multilingual Retrieval Augmented Generation (RAG)
Introduction to Multilingual Retrieval Augmented Generation (RAG)
 
DBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor PresentationDBX First Quarter 2024 Investor Presentation
DBX First Quarter 2024 Investor Presentation
 
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...
 
Corporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptxCorporate and higher education May webinar.pptx
Corporate and higher education May webinar.pptx
 
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
 
FWD Group - Insurer Innovation Award 2024
FWD Group - Insurer Innovation Award 2024FWD Group - Insurer Innovation Award 2024
FWD Group - Insurer Innovation Award 2024
 
ICT role in 21st century education and its challenges
ICT role in 21st century education and its challengesICT role in 21st century education and its challenges
ICT role in 21st century education and its challenges
 
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...
 
CNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In PakistanCNIC Information System with Pakdata Cf In Pakistan
CNIC Information System with Pakdata Cf In Pakistan
 
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
 

Introduction to CI/CD

  • 1.
  • 2. Introduction to CI/CD Steve Mactaggart State Manager - Victoria
  • 3. Agenda ● What is CI and CD ● What makes good CI / CD ● How we get there ● Business benefits of it all….
  • 4. What is CI and CD? ● Continuous Integration ○ An approach to be continually validating the state of a codebase through automated testing. ○ Best achieved through integration with version control ● Continuous Delivery / Deployment ○ An approach to regularly deploying artifacts that successfully pass the CI phase to ensure confidence around the deployment
  • 5. Delivery vs Deployment Continuous integration, continuous deployment, and continuous delivery are like vectors that have the same direction, but different magnitude. Their goal is the same: make our software development and release process faster and more robust. The key difference between the three is in the scope of automation applied.
  • 6. Delivery vs Deployment ● Continuous Delivery ○ Automatically prepare and track a release to production ○ The desired outcome is that anyone with sufficient privileges to deploy a new release can do so at any time in one or a few clicks. By eliminating nearly all manual tasks, developers become more productive. ● Continuous Deployment ○ Every change in the source code is deployed to production automatically, without explicit approval from a developer. ○ As long as it passes the quality controls
  • 7. What does good look like?
  • 8. What makes for good CI? 1. Decoupled stages ○ Each step in CI should do a single focused task 2. Repeatable ○ Automated in a way that is consistently repeatable ○ Tooling should work for local developers too – Local/Remote parity 3. Fail fast ○ Fail at the first sign of trouble
  • 10. What makes for good CD? 1. Design with the system in mind ○ Cover as many parts of a deployment as possible ○ Application | Infrastructure | Configuration | Data 2. Pipelines ○ Continually increase confidence as you move towards production 3. Globally unique versions ○ Know the state of the system at any time ○ Be able to demonstrate difference between current and future state
  • 11. CD Pipeline flow DEV PRE PROD PRODUCTIONConfiguration Infrastructure Application
  • 12. Bringing CI & CD together Continuous Integration Knowing the artifacts are Good Knowing the deployment is Good Continuous Delivery / Deployment Artifact store
  • 14. Tracking Confidence Where do we start? How do we know we are progressing?
  • 15.
  • 16. 1. Assess the current state 2. WSJF 3. Think globally – act locally ○ Proof of Concept and Spikes are your friends
  • 17. 1. Assess the current state 2. WSJF 3. Think globally – act locally ○ Proof of Concept and Spikes are your friends
  • 18. Unit testing and shifting left ● Make the tests easy to run ○ Run them locally ■ Invest in good quality IDE support ○ Consistent entrypoint - Abstract the complexity ■ Makefiles / Gradle ○ Pull request unit test execution
  • 19. Failing fast ● Code inspection ○ Code linting ○ Security inspection ○ Code format ● Code coverage ○ Track coverage changes
  • 20. Centralised artifacts ● Managing output from a CI process ○ Only the strong survive ○ Central common location ○ Clearly understood name and version approach ○ Build them only once ○ Make them timeless – externalise configuration
  • 22. Why do this? ● Reduction of delivery risk ○ No longer do we need to rely on humans with specific knowledge as the gate-keepers of quality ○ Reduced chance of humans not following the process ○ Reduced chance of mis-communication on executing the change
  • 23. Why do this? ● To encode the process, we need to know the process ○ If we know all the tests pass, ○ If we know all the steps in deployment, ○ What is stopping us from releasing?
  • 24. Why do this? ● Better visibility on change ○ As our systems and tools are version controlled ○ And we know what the current state of production is ○ And we can describe the process by which it will be changed ○ We can diff the system states with confidence ● Opens up more avenues for review and increased audit compliance
  • 25. Why do this? ● Increased efficiency and delivery options ○ Enables us to deliver things with reduced effort ○ This leads us to deploy change more frequently ○ Which leads to getting feedback faster ○ That enables us to experiment easier ○ This leads to smaller batch sizes ○ Which leads to and increased flow of the entire system
  • 26. Why do this? ● Enhanced learning from failure ○ When we have an issue or failure, we write a test to cover it ○ This test gets added to our suite and executed every time ○ Decreases our risk of this issue occurring again
  • 27. That’s all folks… Steve Mactaggart State Manager – Victoria steve.mactaggart@cevo.com.au

Editor's Notes

  1. Focus here is CONTINUOUS You'll see this reoccur through todays talk You could do CI without version control, but it would kinda be like cycling without wheels
  2. Give you an example During recent engagements - we were able to get to Delivery All changes ran through the same flow Sequence of the tasks were sometimes different Approval and validation still had manual steps Cevo Website - made it to Deployment Merge to master If it builds, and the tests pass then it is released
  3. Simple Like we are doing in the application space, moving away from monoliths - our CI should follow the same patterns Enables better troubleshooting Powers greater reuse Repeatable Where most of your time will end up being sunk This is the tools Environment isolaiton Dependancy isolation Version consistency Fail fast Lean in to the pain, better to have it earlier
  4. Simple Test a single function well at the unit level Repeatable Isolate from Data / Systems / Availability Fail Fast Time to fail in unit is super quick We should only be moving something forward if we know it is as good as it can possibly be. Lots of awesome tooling and prior art in this space, challenge is that not all code is testable in its current state - requires some investment in closing the gap (Tech Debt)
  5. Systems are no longer only the application Think network egress rules Encryption keys O/S packaging updates Even compute / memory requirements Pipelines Everything goes the same path, if it fail we throw it all out and look for the next item Visualise the pipeline Enable us to build in stage gates of quality along the way Like point #1 - a system is not one thing What is the version of the system 1/2/3? * as code enables a diff based review process
  6. Green = CI Yellow / Red = CD yellow may repeat in complex environments SIT / UAT / PRE environments But the process should be the same Focus on Pull based deployments, not push based workflows
  7. Channel the Repeatable focus Try hard to have the one process to run them all Common entry point Keep it simple Don't have lots of complex config Fail fast Run tests against branches to get confidence before merge Keep your tests versioned with your code
  8. Don't be re-building the artifact because you change passwords – inject this configuration