(Optional) Number of times to retry downloading a build artifact if the download fails. (Optional) If checked, this build task will check that all files are fully downloaded. See Artifacts in Azure Pipelines.Īrgument aliases: targetPath, downloadPath If multi-download option is applied (by leaving an empty artifact name), a sub-directory will be created for each. Can be relative to the pipeline workspace directory or absolute. (Required) Directory to download the artifact files. More Information on file matching patterns (Optional) One or more file matching patterns (new line delimited) that limit which files get downloaded. If left empty, all artifacts associated to the pipeline run will be downloaded. (Optional) The name of the artifact to download. (Optional) If checked, this build task will try to download artifacts whether the build is succeeded or failed
(Optional) If checked, this build task will try to download artifacts whether the build is succeeded or partially succeeded Only builds with these tags will be returned.ĭownload artifacts from partially succeeded builds (Optional) A comma-delimited list of tags. (Required) The build from which to download the artifacts. Options: latest, latestFromBranch, specific (Required) Specifies which build version to download. (Optional) A boolean specifying whether to download artifacts from a triggering build.Īrgument aliases: specificBuildWithTriggering When appropriate, download artifacts from the triggering build (Required) The definition ID of the build pipeline. (Required) The project name or GUID from which to download the pipeline artifacts. (Required) Download artifacts produced by the current pipeline run, or from a specific pipeline run.
For more information, see Publish and Download in the YAML schema. You can use them in your pipeline to publish and download artifacts. The publish and download keywords are shortcuts for the Publish Pipeline Artifact task.
0 kommentar(er)
