Scribd
Upload
121 views1 page

CICD Process Flow: Code Build Test Deploy Provision

This document summarizes a CI/CD process flow involving code commits, builds, tests, and deploys. Key steps include: 1. Developers push code to AWS CodeCommit which triggers AWS CodePipeline. 2. CodeBuild automatically builds Docker images which are saved to ECR. 3. If tests pass, the develop branch is merged to staging and deployed to a test environment via CodeDeploy. 4. If tests pass in the staging environment, the staging branch is merged to master and deployed to production.

Uploaded by

vPaiyan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
121 views1 page

CICD Process Flow: Code Build Test Deploy Provision

This document summarizes a CI/CD process flow involving code commits, builds, tests, and deploys. Key steps include: 1. Developers push code to AWS CodeCommit which triggers AWS CodePipeline. 2. CodeBuild automatically builds Docker images which are saved to ECR. 3. If tests pass, the develop branch is merged to staging and deployed to a test environment via CodeDeploy. 4. If tests pass in the staging environment, the staging branch is merged to master and deployed to production.

Uploaded by

vPaiyan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

CICD Process Flow

Code Build Test Deploy Provision

Orchestrator

Check manually. If apps


AWS CodeCommit AWS CodeBuild AWS CodeDeploy work properly, merge
develop branch to staging
AWS branch.
CodePipeline

Running on Build Docker


① Push Auto
Build images
(AWS managed)
Image from instructions in Auto ② Confirm
buildspec.yml
Group: Developer group Deploy
IAM role: CodeCommit Develop branch
Testers

Save images Download images


Dev1 Send notifications Save logs AWS EKS
AWS Credential 1 Elastic Kubernetes Service
(Develop environment)

Dev2
AWS Credential 2 AWS ECR
Email AWS AWS S3 Elastic Container Registry Check manually. If apps
AWS SNS Notification CloudWatch Bucket  work properly, merge
staging branch to master
Dev3
branch.
AWS Credential 3

③ Merge Auto Auto build & test for staging environment. Auto Auto deploy & provision for staging environment. ④ Confirm
Do the same thing to develop environment Do the same thing to develop environment
Master branch
Testers

Download images

Use the same images


 which are built for staging
Deploy
environment to deploy to
production environment ⑤ Confirm

AWS EKS Testers


Elastic Kubernetes Service
(Production environment)
Check manually. If apps
do not work properly,
V1 V2 swap to the previous
stable version.

V1 V2

You might also like