CdCon 2020 Lightning Talk: CI/CD Patterns
0 likes34 views
The document discusses CI/CD patterns and provides strategies for implementing continuous integration and continuous delivery pipelines. It outlines challenges like high costs and slow development when teams perform both development and operations work. This can lead to delayed business value and lower productivity. The document then recommends measuring pain points, minimizing complexities and maintenance needs in pipelines, and designing default pipelines to deploy changes in order to address these issues.
CdCon 2020 Lightning Talk: CI/CD Patterns
- 1. Confidential / © Harness Inc. 2020 CI/CD Patterns A Lightning Talk By Tiffany Jachja Evangelist @ Harness.io
- 2. Confidential / © Harness Inc. 2020 Confidential / © Harness Inc. 2020
- 3. Confidential / © Harness Inc. 2020 The Challenges • High maintenance and integration costs • Slow/Block Development teams • Developers doing Ops
- 4. Confidential / © Harness Inc. 2020 The Impacts • Delayed business value • TOIL. Lowered productivity & happiness • Less reliable software
- 5. Confidential / © Harness Inc. 2020
- 6. Confidential / © Harness Inc. 2020
- 7. Confidential / © Harness Inc. 2020
- 8. Confidential / © Harness Inc. 2020 M1 – Measure. The pain points • CI or CD: Build, test, deployment? • Speed, security, compliance? • The DevOps Metrics & SLOs
- 9. Confidential / © Harness Inc. 2020 M2 – Minimize. Development should be easy • Minimize branching • Minimize maintenance on e2e tests and scripts • Minimize builds in a pipeline
- 10. Confidential / © Harness Inc. 2020 M3 – Make. Pipelines are the only way to deploy • Make default CI/CD pipelines • Make tests run fast, early, clean • Make parity between stage and production
- 11. Confidential / © Harness Inc. 2020
- 12. Confidential / © Harness Inc. 2020 P/12 Confidential / © Harness Inc. 2020 P/12 @tiffanyjachja THANK YOU Confidential / © Harness Inc. 2020C P/12 — Any Questions / Contact: tiffany.jachja@harness.io