The Pre-deploy step executes a single named project from the snapshot to the stage. The project has to configure Pre-deploy Workflow in the project configuration screen for the step to run.
...
| Tip |
|---|
Pre-deploy uses a named project which reduces the generic nature of pipelines, as it requires that the specific project is in the release and snapshot. To make the pipeline more generic, and therefore reusable, you should try to avoid tying it to specific projects where possible by using the Pre-deploy All step instead. The Pre-deploy step allows the output from the Pre-deploy workflows to flow into the Deploy workflow inputs for each project. For this to work, workflow developers must use the same name and data type for the Pre-deploy output(with "Return As Output" selected) and Deploy input variables in the respective workflows. |
Script Variables
| Include Page | ||||
|---|---|---|---|---|
|