GCP DevOps Project
Sprint 03
Sprint 03 Review
Welcome back! In Sprint 03, we completed the design discussion around CI/CD on Google Cloud Platform (GCP), defined our problem statement, evaluated native GCP services, and selected the tools for an automated pipeline.
Completed Work
We mapped out Continuous Integration and Continuous Deployment as an “infinity loop” to show how commits flow through build, test, and deploy stages—emphasizing feedback loops and full automation.
Next Sprint: Implementation Roadmap
In Sprint 04, we’ll shift focus to hands-on setup using GCP services. Below is our task breakdown:
| Task | Objective | Key Activities |
|---|---|---|
| Explore Cloud Build | Learn GCP’s managed CI service | • Configure build triggers<br>• Define steps & substitutions<br>• Author cloudbuild.yaml |
| Understand Artifact Registry | Compare to Container Registry | • Review repository types & regions<br>• Set IAM permissions<br>• Discuss supported artifacts (Docker, Maven, npm, etc.) |
| Implement Build & Push Pipeline | Automate Docker image creation and publishing | • Fetch source from GitHub<br>• Build with cloudbuild.yaml<br>• Tag & push to Artifact Registry |
Note
Make sure your cloudbuild.yaml is correctly indented. Even a single space error can cause build failures.
Warning
Verify IAM roles for Cloud Build and Artifact Registry. Missing permissions will block image pushes.
The conceptual flow below illustrates how Cloud Build retrieves code from GitHub, builds a Docker image via cloudbuild.yaml, and securely pushes it to Artifact Registry with proper tagging and permissions.
That wraps up our Sprint 03 review. In the next lesson, we’ll deep-dive into Cloud Build configuration and create our first automated pipeline. See you soon!
Links and References
Watch Video
Watch video content