An engineering team is building a secure CI/CD pipeline on Google Cloud Platform to deploy a microservice to Cloud Run. Arrange the following SDLC pipeline stages in the correct chronological order from developer commit to full production deployment.
- 1Developer commits source code changes to Cloud Source Repositories.
- 2Cloud Build executes automated unit tests and builds the container image.
- 3Artifact Analysis scans the container image for vulnerabilities before storing it in Artifact Registry.
- 4Cloud Build deploys a new revision to Cloud Run with a 10% canary traffic split.
- 5After monitoring health metrics, Cloud Build updates the traffic split to route 100% of traffic to the new revision.
Cevap
The correct chronological sequence for the GCP CI/CD deployment pipeline is: 1) Developer commits source code to Cloud Source Repositories, 2) Cloud Build executes unit tests and builds the container image, 3) Artifact Analysis scans the image for vulnerabilities before storing in Artifact Registry, 4) Cloud Build deploys the new revision to Cloud Run with a 10% canary traffic split, and 5) Cloud Build routes 100% of traffic to the new revision after health checks pass.
The correct sequence follows Google Cloud CI/CD best practices: Source Commit -> Build & Test -> Security Vulnerability Scan -> Canary Traffic Deployment -> 100% Traffic Promotion.
Adım Adım Çözüm
Anahtar Kavram
Sequencing CI/CD pipeline stages from source code trigger to vulnerability scanning and canary deployment on GCP.