Here is the example pipeline we will talk at high level. It is entirely up to process that you want to implement in your organization, this is just one example.
In this pipeline, we will have 4 roles which makes up our Team.
...
Steps used are for Deploying All Projects and Test All to execute Integration Tests. Deploy All Step will deploy all projects in Release as per Deploy Priority setup on Release, which will allow for Sequenced deployments.
QA
First thing we want to do is to check for Tests executed in Test environment and move on only if Tests were successful. Then we will use Approval Gate by QA role, so that allows QA team to control promotion of code in QA environment as per their testing schedule.
Steps used are for Deploying All Projects and Test All to execute Functional Tests. Deploy All Step will deploy all projects in Release as per Deploy Priority setup on Release, which will allow for Sequenced deployments. Additionally we will use Manual Step to allow for some manual verification in QA environment.
Production
First thing we want to do is to check for Tests executed in QA environment and move on only if Tests were successful. Then we will use Approval Gate by Operator role, so that allows Operators to control promotion of code in Production environment. Next we will have Schedule Gate to run steps only Saturday at 9 PM which would allow for code promotion at predefined downtime.
Steps used are for Deploying All Projects and Test All to execute Smoke Tests. Deploy All Step will deploy all projects in Release as per Deploy Priority setup on Release, which will allow for Sequenced deployments. We will only run simple verification tests (aka Smoke Tests). Additionally we will use Notification Step to allow for send completion email to Operators.
