Follow these steps to reconcile your pipeline configuration and resolve the source name. 1. Verify the Artifact Name
The error message "download pipeline artifacts shortcut cannot resolve source name" typically occurs in CI/CD environments like Azure DevOps when a YAML pipeline attempts to download an artifact from a source that the system cannot identify or access. This usually stems from a mismatch between the artifact's published name and the download task's configuration. Follow these steps to reconcile your pipeline configuration
While shortcuts like - download: current are convenient, they can be ambiguous in complex multi-stage or multi-repo setups. Switching to the explicit DownloadPipelineArtifact@2 task often resolves resolution issues by providing more metadata. This usually stems from a mismatch between the
Mention if you're working across or repositories Mention if you're working across or repositories :
: Pipeline artifact names are often case-sensitive; "WebApp" and "webapp" are seen as different sources.
Before diving into deep troubleshooting, check these frequent culprits that trigger source name errors: