DATASTAR: Get Sources
For a given work item, the task pulls every .xml release control file attached to that work item, produces one .mf manifest per release control file, and lays out the script folder structure that the manifests reference.
A typical deployment file looks like:
<Deployment VcsType="tfs">
<Item Version="{CHANGESETID}" Path=""/>
</Deployment>
Inputs
Required inputs marked with *.
| Input | Required | Description |
|---|---|---|
| Manifest Path* | Yes | The $-prefixed version-control path to the manifest file (or its folder). |
| Source Path* | Yes | The target directory for the downloaded scripts. |
Advanced options
| Input | Description |
|---|---|
| Fail on Standard Error | Fail the task if anything is written to stderr. |
| Clean Source Directory | Delete existing files in the source directory before pulling. |
| Repository Uri | The Azure DevOps collection URI. Defaults to SYSTEM_TEAMFOUNDATIONCOLLECTIONURI. |
| Bearer Token | Optional OAuth token. Set to $(System.AccessToken) to use the pipeline's built-in token. |
| User Name | Used for basic auth. If set, Password must also be set. |
| Password | Basic-auth password. Store as a secret variable. |
| Use Proxy Server | Route the request through the agent's web proxy. |
| Proxy Uri | Override the proxy URI. |
| Proxy Username / Password | Proxy credentials, if not using defaults. |
Support
Report problems to support@absolute.technology.