Journey towards CI/CD
summary
Project starts without version control and copies files by hand, causing broken features and team conflict; the fix is to add git for versioning, containerize with Docker, and automate infra with Terraform plus GitHub Actions to push images to ECR and run on AWS ECS. Pipelines use branch name as Terraform state key and image tag to create ephemeral, branch-based environments on one click (demo deploys in ~3 minutes), which cuts debugging time, prevents overwrites, and makes rollbacks straightforward.
AI-written summary · about
chapters (12)
- 0:00Introduction to journey
- 3:57Starting with no version control
- 9:02Adding Git to the project
- 10:50Virtual machine configuration struggles
- 11:54Introducing Docker containers
- 14:00Developer vs operations blame game
- 16:33Developer access to production
- 17:36Automation with CI/CD pipelines
- 20:30Demo introduction
- 23:40Demo walkthrough
- 32:38CI/CD as a mindset
- 35:11Q&A and closing remarks
related talks
33mBuilding Automated Pipelines for Infrastructure Code with Terraform and Packer
36mTerraform & CI/CD
46mImplementing Infrastructure as Code
48mHow to build solid CI-CD pipeline
02h 47mPipes on Pipelines
35mBeyond build/test/deploy
39mRemove your Testing Bottleneck with CI/CD Pipelines
32mCreate an Infrastructure Pipeline with GitHub Actions and Terraform