Create a release in Azure DevOps.
Target Properties
Property Name | Property Code | Required | Description |
---|---|---|---|
Azure DevOps Cloud Account |
| Yes | The Azure DevOps account with all the required properties like Organization, and Personal Access Token for running Azure DevOps Instance. |
Interval between Release Environment Status check |
| No | The Interval between Release Environment Status check. |
Number of Iterations |
| No | The Number of Iterations to perform the Release Status check. |
API Version |
| No | The API version of the Azure DevOps REST API. Defaults to 7.0. |
Inputs
Input Name | Input Code | Required | Description |
---|---|---|---|
Azure DevOps Release Definition Id |
| Yes | The ID of the Release Definition. |
Azure DevOps Release Artifacts Payload |
| No | Provide Artifacts Metadata JSON payload of the Package to be deployed. |
Check for Release Status |
| No | Check for the Release Status. Defaults to false. |
Azure DevOps Release Manual Environments |
| No | Provide comma separated list of environments e.g. DEV,QA etc. |
Azure DevOps Release Properties List |
| No | Provide properties collection JSON payload. |
Azure DevOps Project Name |
| Yes | The Name of the Project. |
Azure DevOps Release Variables List |
| No | Provide variables JSON payload or double hash (##) separated variable key-value pairs of variable-group. e.g. var1:value1##var2:value2. |
Consider environments with the status partiallySucceeded as succeeded |
| No | Provide the environments allowed as succeeded for a partially succeeded status. Use commas to separate multiple environments (e.g: DEV, QA). Use ALL to denote all the environments. Note: This is only applicable when 'Check for Release Status' is selected. |
Outputs
Output Name | Description |
---|---|
| POST request REST API response. |
| The Release Web URL to navigate to the Azure DevOps Create Release Flow. |
| JSON Payload of Release Environment Stage Details. (e.g. [{“id”:123,”name”:”DEV”}] |
| The ID of the Release in Azure DevOps. |
Artifacts
This operation does not produce or consume any artifacts.
Endpoint Selection
This operation will select all available endpoints associated to the target.
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.