Downloading a pipeline artifact in Azure DevOps can be done through the Azure DevOps interface or programmatically using Azure DevOps REST API or Azure CLI. Here’s a step-by-step guide to downloading a pipeline artifact:

Downloading via Azure DevOps Interface

1. Navigate to Your Build:

   • Go to the Azure DevOps portal.
   • Navigate to the “Pipelines” section and then to “Builds” or “Releases” depending on where your artifact is published.

2. Select the Build/Release:

   • Choose the specific build or release that contains the artifact you want to download.

3. Find the Artifacts Section:

   • Look for the “Artifacts” section in the build or release summary page.

4. Download the Artifact:

   • Click on the artifact you want to download. There should be an option to download the artifact, either as a single file or a zip file.

Downloading via Azure DevOps REST API

1. Use the Artifact API Endpoint:

   • Azure DevOps provides a REST API endpoint to get artifacts.
   • The endpoint typically looks like this: GET https://dev.azure.com/{organization}/{project}/_apis/build/builds/{buildId}/artifacts?artifactName={artifactName}&api-version=6.0.

2. Construct the Request:

   • Replace {organization}, {project}, {buildId}, and {artifactName} with your specific details.
   • You can get the buildId from the URL of your build in Azure DevOps.

3. Authentication:

   • Use a Personal Access Token (PAT) for authentication. Include it in the header of your HTTP request.

4. Execute and Download:

   • Execute the HTTP request.
   • The response will include a URL to directly download the artifact.

Downloading via Azure CLI

1. Install Azure CLI:

   • Ensure that you have Azure CLI installed and configured.

2. Use Azure DevOps Extension:

   • You might need the Azure DevOps extension for Azure CLI. Install it using az extension add --name azure-devops.

3. Run the CLI Command:

   • Use the Azure CLI command to list and download artifacts.
   • Example command: az pipelines runs artifact download --run-id {runId} --artifact-name {artifactName}.

4. Specify Run ID and Artifact Name:

   • Replace {runId} with the ID of the pipeline run and {artifactName} with the name of the artifact.

In all methods, make sure you have the necessary permissions to access the build or release and its artifacts. If you’re using the API or CLI methods, your Personal Access Token should have appropriate scopes for accessing build artifacts.