Sheet1

Azure Pipelines – CICD

Sequence
Branch Trigger Action 1
develop Pull Request Run Unit Test 2
Check Code Quality 3

develop ? Run Scenario Test 4

master Pull Request Run Performance Test 5

Run Load Test 6

Run Stress Test 7
8
9
10
11
12
13

14
15
16
17
18
19

Page 1
 Sheet1

Description
Developer create a new feature branch feature-A from branch develop
Developer commits the branch feature-A
Developer raises a PR for branch develops
Azure pipelines should run all the unit test and perform code quality checks.
If PASS then proceed and notify the reviewer (on SLACK channel) ELSE notify the developer (who raised the PR) on SLA
Reviewer waits for the above to pass then perfroms manual code review and then “Rebase and Merge” the code to branch
Before Rebase and Merge, Azure Pipeline should run all the Scenario Test.
If PASS then proceed ELSE raise a Bug in Azure (automatically) and assigned it to the developer who raised the PR
Rebase and Merge the code on branch develop
Azure pipelines should create a docker image and push it to Azure Container Registry
Azure pipelines should deploy and run the docker on TEST environment.
Azure pipelines should Notify that “New Build” has been deployed (on SLACK channel)
QA team will manually test the application
QA Team will certify the build (manual process) and notify the development team (manual process)
Developer raises a PR from branch develop to branch master
Azure pipelines should run Performance test, Load test and Stress test
If PASS then proceed ELSE raise a Bug in Azure (automatically) and assign it to the developer who raised the PR.
Rebase and Merge the code on branch master
Azure pipelines should create a docker image and push it to Azure Container Registry
Azure pipelines should deploy and run the docker on STAGE environment.
Azure pipelines should create a release notes using all the Work Items tagged in the comments.
Azure pipelines should Notify that “New Release” has been deployed (on SLACK channel)

Page 2