Practical Tips & Tricks for CI/CD Success • Zan Markan • GOTO 2022

This presentation was recorded at GOTO Amsterdam 2022. #GOTOcon #GOTOams

Zan Markan - Developer Advocate at CircleCI

ABSTRACT
A CI/CD pipeline seems straightforward to implement and maintain. Yet it can often quickly become a tedious time sink and a source of universal frustration on many teams. From flaky builds, to long running builds, to flaky long running builds, the sources of frustration are endless. With the goal to ship more and faster as well as to compete in an ever changing industry, we can (and must) do better.

This talk will cover best practices for performance, stability, security, and maintainability of CI/CD pipelines, each supported with practical examples and counterexamples.

Some examples of topics covered:
• Integrating security scanning as part of the build and test automation
• Techniques for speeding up the builds and faster recovery from failures
• The importance of getting the whole team involved in the CI/CD process
• Understanding the bottlenecks and areas for improvement both in the CI/CD pipelines and across the organization
• Planning for failure and reverting broken deploys [...]

TIMECODES
00:00 Intro
07:35 Continuous Integration
08:43 Continuous Deployment
09:15 Multiple dimensions of CI/CD success
09:41 Speed
11:33 Running your pipelines faster
15:40 CI/CD is like an ambulance
17:20 Recovering from failures
20:25 Security & risk management
23:36 Beyond the CI/CD tool
26:02 DevOps is about people
28:15 Revert what's broken
30:15 CI/CD success = freedom
31:18 Outro

Download slides and read the full abstract here:

RECOMMENDED BOOKS

#ContinuousDelivery #CD #CICD #BDD #DevOps #Testing #StateOfDevOps #StateOfDevOpsReport #Programming #SoftwareEngineering #CDPipelines #DeploymentPipelines #CloudNative #CircleCI

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[ShibeInu]

5 minutes of information stretched into 32 mins of presentation

[elliotalderson]

Actually „CI“ has nothing to do with „isolated environments“ or „docker images“ - it’s about merging all different code changes into a shared main branch early and often (e.g. several times a day).