The Plumbers Guide to the Galaxy

Implementing a CI/CD Pipeline with GitHub

GitHub makes it easy to collaborate on code, but its true power comes when used as the centerpiece of a modern deployment pipeline. This class will start with an overview of the concepts behind continuous integration (CI) and continuous delivery (CD), two cornerstones of good software development. After that, we'll cover how to start incorporating these practices into your workflow, by using GitHub to integrate with best-of-breed 3rd party tools. This class is designed for those with intermediate Git and GitHub knowledge, but limited hands-on experience implementing CI/CD practices.

Transcript

1. The Plumbers Guide to the Galaxy Implementing a CI and CD Pipeline with GitHub September 13 2016
2. Hector Alfaro Stefan Stölzle ! " ! stoe stefan@github.com @me_stoe ! " hectorsector hectorsector@github.com
3. Pre-Requisites !
4. Legacy SDLCs
5. ancient • have a VCS (!) • 1 branch/trunk/mainline • ~ year scale release cadence
6. waterfall • several long-running branches • human gates • ~ month scale release cadence (at best)
7. what do we want?
8. CI/CD benefits # $ % better feedback at all stages shorter cycle time granular releases
9. CI/CD benefits & ' ( less stress more time for creative work measure success/failure consistently
10. CI/CD benefits Cost per Defect $0 $2,000 $4,000 $6,000 $8,000 $10,000 $12,000 $14,000 $16,000 Requirements Design Coding Testing Maintenance $139 $455 $977 $7,136 $14,103 taken from https://agileelements.wordpress.com/2008/04/22/cost-of-software-defects/ adapted from Jones, Software Assessments, Benchmarks, and Best Practices (2000)
11. continuous delivery/deployment automated software delivery process • frequent branching + pull requests • primarily automated gates • ~ minute scale release cadence
12. Fig 5.2 Humble, Farley Continuous Delivery (2010) Trigger Trigger Trigger Trigger Trigger Check in Check in Check in Feedback Feedback Feedback Feedback Feedback Feedback Approval Approval Delivery Team Version Control Build &
 Unit Tests Automated Acceptance Tests User Acceptance Tests Release
13. CI/CD with GitHub Hub of SDLC
14. Getting started Create a Branch Open a Pull Request Merge and deploy
15. Integrate new practices & tools Protected Branches automated gates Status API 
 CI Create a Branch Open a Pull Request Merge and deploy
16. Let’s try universe-plumbers-guide.herokuapp.com/
17. Template GitHub repository universe-plumbers-guide.herokuapp.com
18. Import the template GitHub repository import.github.com
19. CI aims ) * + catch bugs early reduce merge conflicts regularly prove app working
20. CI in practice (cultural) • agreed failure threshold • test locally first • don’t base new work on broken build • revert if needed • share code ownership
 CI a process, not a tool!
21. CI in practice (technical) • short-lived branches (< 3 days) • build/test every push • display results prominently
22. GitHub Deployments API Fig 5.2 Humble, Farley Continuous Delivery (2010) Create Deployment Deployment Created Deployment Event SSH + Deploy Deployment Status Deployment Status Deploy Completed Tooling GitHub 3rd Party Your Server
23. Thank you! ! " ! Stefan Stölzle stoe stefan@github.com @me_stoe ! " Hector Alfaro hectorsector hector@github.com