The document summarizes a presentation on CI/CD and its role in DevOps. It began with an agenda for the Upstate DevOps meetup, including a session on CI/CD. It then discussed how software deployment used to work, and how CI/CD automates the process. It defined CI as continuous integration, automating testing and merging code changes. It defined CD as either continuous delivery, where code is ready for production, or continuous deployment, where code is automatically deployed to production. The presentation argued CI/CD provides benefits like faster fixes and more reliable releases. It concluded with considerations for CI/CD and resources for learning more.

1. UPSTATE DEVOPS!
WELCOME TO

2. UPSTATE DEVOPS - NOVEMBER 7, 2019
TODAY’S AGENDA
▸ 11:45 - 12:00 PM ~ Lunch & Networking
▸ 12:00 - 12:45 PM ~ CI/CD and its role in DevOps
▸ 12:45 - 1:00 PM ~ Q/A & Dismissal
▸ Thanks to our sponsors!
2

3. CI/CD AND ITS
ROLE IN DEVOPS

4. UPSTATE DEVOPS - NOVEMBER 7, 2019
HOW WE USED TO STILL DEPLOY SOFTWARE…
L33t Coders create code.
>git commit -m “my code yo”
>git push origin
Pitching it over to the Ops team
Minutes, hours, days?!? Rollback?!

5. UPSTATE DEVOPS - NOVEMBER 7, 2019
BUT IF YOU WANT TO “ACHIEVE DEVOPS”…
START THINKING ABOUT AUTOMATING THIS PROCESS

6. UPSTATE DEVOPS - NOVEMBER 7, 2019
SO WHAT IS CI/CD?
▸ The process of frequently delivering
applications to end-users by introducing
automation into the various stages of
software development.
▸ In a nutshell - You commit code. Magic
Happens. Out spits a deployed
application. (Don’t we all wish it was this
simple)

7. UPSTATE DEVOPS - NOVEMBER 7, 2019
WHAT IS CI?
▸ CI = Continuous Integration
▸ Automating code builds, testing, merges in a shared repo.
▸ A dev pushes their code up. The CI server sees the changes and
pulls it down. Then runs tests, builds, merges branches, etc. If it
succeeds it moves to the next step. If it fails it stops (and alerts fire!)

8. UPSTATE DEVOPS - NOVEMBER 7, 2019
WHAT IS CD? (PART 1)
▸ CD = Continuous Delivery
▸ Once the build is clean the ‘bug-free’ code is uploaded to a repo or artifact
storage, container image repository and is ready to deploy to production.
▸ Ops teams can now pull the latest and deploy at their leisure to production.
No more waiting for the devs.
▸ Software is continuously being delivered and ready to roll to production
(https://cd.foundation/projects/)

9. UPSTATE DEVOPS - NOVEMBER 7, 2019
WHAT IS CD? (PART 2)
▸ CD = Continuous Deployment
▸ Once the build is clean the ‘bug-free’ code is uploaded to a repo or artifact
storage, container image repository and is ready to deploy to production.
▸ Software is continuously being deployed and rolled out to production all the time.
▸ With or without manual intervention. Although having someone press the green
button might not be a bad idea.
(https://cd.foundation/projects/)

10. UPSTATE DEVOPS - NOVEMBER 7, 2019
IT’S A PIPELINE OF IMPROVEMENT (WHY YOU NEED IT)
▸ Detect errors sooner. Fix them faster.
▸ Reduce integration problems.
▸ Avoid compounding problems.
▸ Ensuring every change is releasable. Test all the
things!
▸ Lower production release risk. Make it boring again.
▸ Deliver value faster by having reliable deployments
and releases.
▸ Tighter customer feedback loops. Rapidly respond
to those feedback loops with more builds.

11. UPSTATE DEVOPS - NOVEMBER 7, 2019
THINGS TO CONSIDER:
▸ Testing - If you aren’t testing or primarily manual testing this will hinder CI/CD efforts. Start
writing unit tests, integration tests, and automating your testing platform.
▸ Security - The pipeline is now a tasty target. If bad actors get into the pipeline (MITM, etc)
they could wreak havoc without you knowing it. Use tools to scan and monitor all steps in
the pipeline.
▸ Easy use cases - CI/CD can become complex fairly quickly and overwhelming. Like many
processes in the DevOps world, starting small and adding complexity will save you a lot of
headaches later on.
▸ Tools - Leverage tools you already are using. There are tools everywhere but you can get tool
overload.
▸ Metrics - Have good observability into your pipelines. Monitor, logging, telemetry, feedback.
▸ Microservices and Container-based applications are great candidates for CI/CD processes.
▸ Fear not - It’s not to late to start. You’d be surprised how many enterprises are still doing
things manually…

12. UPSTATE DEVOPS - NOVEMBER 7, 2019
DEMO TIME!
(Hopefully it won’t blow up…)

13. UPSTATE DEVOPS - NOVEMBER 7, 2019
RESOURCES:
▸ cd.foundation - https://cd.foundation/projects/
▸ Git Hub Actions (in beta) - https://lab.github.com/github/
hello-github-actions!
▸ Bitbucket Pipelines - https://bitbucket.org/product/features/
pipelines
▸ Gitlab CI - https://docs.gitlab.com/ee/ci/quick_start/
▸ Dozens more out there…Team City, Bamboo, Jenkins, Travis
CI, Go CD, Spinnaker, etc.

14. THANK YOU!
@VALIEN
@UPSTATEDEVOPS
WWW.MEETUP.COM/UPSTATE-DEVOPS