Release gates allow controlled automatic collection of health signals from external services,
and promote the release when all signals indicate a healthy deployment.
In this example, we'll add a release gate to validate code coverage on a module before deployment.
Add gate to the release pipeline
Once the extension is installed on your account, you can add the new gate to your release pipelines.
Enable Gates and add Code Coverage to the gate.
The release would wait for the cumulative code coverage for the chosen module
to reach the threshold before proceeding to the next stage. Configure the gate as shown below.
Select the build artifact
(Case sensitive) Name of the module or dll to evaluate
Code Coverage Type
Line : to evaluate the number of lines not covered
Block : to evaluate the number of blocks not covered
Set the maximum threshold for line or blocks to pass the gate
Gates in action
When the number of lines not covered is less than the threshold, the gate is passed.
Example : Lines not covered - 37
Threshold - 38 - Pass
When the number of lines not covered is greater than the threshold, the gate is failed.