CI/CD Best Practices to Deliver Software Faster
summary
Defines CI as builds under 10 minutes, recommends build once and promote the same artifact through all stages, and insists on commit early/commit often with automated tests that run quick tests first before longer suites. Uses Git/GitHub, Jenkins, Maven/Gradle, JUnit/Selenium, SonarQube, Nexus, Docker, Kubernetes and GCP/AWS/Azure, plus IaC for ephemeral test environments. Tracks builds-per-day, deployment speed and flaky tests, forbids bypassing pipeline and treats pipeline health as a team responsibility.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:44Continuous Integration
- 3:35Delivery vs Deployment
- 9:38CI/CD benefits
- 10:22Secure CI/CD pipelines
- 17:50Collaborative CI/CD culture
- 18:32CI/CD pipeline tools
- 22:08Conclusion and key takeaways
related talks
48mDemystifying CI/CD
17mCI/CD - Build/Deploy Automation
51mBetter software, faster: principles of Continuous Delivery and DevOps
32mPractical Tips & Tricks for CI/CD Success
01h 10mCreating efficient, convenient and reliable CI
01h 05mTwelve Essential Practices to be Effective in Continuous Delivery
15mCI/CD: A History Lesson
44mSimplifying and Scaling Software Delivery