You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2020. It is now read-only.
VSTS has a mechanism on Release Management which allows to stop a Release until certain condition is met, these are Deployment Gates.
These conditions can be based on the results of the json from an API REST call, which is a little bit tedious to configure.
It would be interesting to create a VSTS Extension, to be able to set up gates based on the results (healthy or not at this moment) for a particular configured Pulse, something like this:
This will allow deployments to be stopped if any condition from previous environments is not met before deployment, based on dependencies tracked by BeatPulse.
The text was updated successfully, but these errors were encountered:
VSTS has a mechanism on Release Management which allows to stop a Release until certain condition is met, these are Deployment Gates.
These conditions can be based on the results of the json from an API REST call, which is a little bit tedious to configure.
It would be interesting to create a VSTS Extension, to be able to set up gates based on the results (healthy or not at this moment) for a particular configured Pulse, something like this:
This will allow deployments to be stopped if any condition from previous environments is not met before deployment, based on dependencies tracked by BeatPulse.
The text was updated successfully, but these errors were encountered: