258 questions
Release pipeline fails to download artifacts from multiple private GitHub repositories
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 56.00000000000001%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENG%3C/text%3E%3C/svg%3E)
Nikolay Gurinov
0
Reputation points
We are experiencing a critical issue in Azure DevOps Release pipelines when using multiple private GitHub repositories as artifact sources.
Working scenarios:
- Existing (older) release pipelines that reference 2 or more private GitHub repositories continue to work without issues.
- A new release pipeline with only one private GitHub repository as an artifact works correctly.
- A new release pipeline with 2 or more public GitHub repositories works correctly.
Failing scenarios:
- Adding a new private GitHub repository to an existing release pipeline with other private GitHub repositories causes the release to fail during artifact download, even if the previously added repos still work.
- Creating a new release pipeline and adding 2 or more private GitHub repositories as artifacts causes the pipeline to fail with the following error:
2025-04-29T13:52:50.8898897Z ##[error]Downloading artifacts failed: System.InvalidOperationException: NotFound
at Microsoft.VisualStudio.Services.Agent.Worker.Release.Artifacts.GitHubHttpClient.GetUserRepo(String accessToken, String repositoryName) in /mnt/vss/_work/1/s/src/Agent.Worker/Release/Artifacts/GitHubHttpClient.cs:line 36
at Microsoft.VisualStudio.Services.Agent.Worker.Release.Artifacts.GitHubArtifact.GetArtifactDetails(IExecutionContext context, AgentArtifactDefinition agentArtifactDefinition) in /mnt/vss/_work/1/s/src/Agent.Worker/Release/Artifacts/GitHubArtifact.cs:line 108
at Microsoft.VisualStudio.Services.Agent.Worker.Release.ReleaseJobExtension.<>c__DisplayClass47_0.<ConvertToArtifactDefinition>b__1() in /mnt/vss/_work/1/s/src/Agent.Worker/Release/ReleaseJobExtension.cs:line 509
at Microsoft.VisualStudio.Services.Agent.Worker.Release.RetryExecutor.Execute(Action action) in /mnt/vss/_work/1/s/src/Agent.Worker/Release/RetryExecutor.cs:line 41
at Microsoft.VisualStudio.Services.Agent.Worker.Release.ReleaseJobExtension.ConvertToArtifactDefinition(AgentArtifactDefinition agentArtifactDefinition, IExecutionContext executionContext, IArtifactExtension extension) in /mnt/vss/_work/1/s/src/Agent.Worker/Release/ReleaseJobExtension.cs:line 506
at Microsoft.VisualStudio.Services.Agent.Worker.Release.ReleaseJobExtension.DownloadArtifacts(IExecutionContext executionContext, IList`1 agentArtifactDefinitions, String artifactsWorkingFolder) in /mnt/vss/_work/1/s/src/Agent.Worker/Release/ReleaseJobExtension.cs:line 257
at Microsoft.VisualStudio.Services.Agent.Worker.Release.ReleaseJobExtension.DownloadArtifactsAndCommitsAsync(IExecutionContext executionContext, Object data) in /mnt/vss/_work/1/s/src/Agent.Worker/Release/ReleaseJobExtension.cs:line 130
2025-04-29T13:52:50.8927104Z ##[error]NotFound
Additional details:
- The GitHub service connection used is the same across all pipelines (both working and failing).
- The service connection has sufficient permissions and the repos are visible in the UI when selecting the artifact.
- The default branch and version are correctly set.
- All tested GitHub repositories contain commits and valid HEAD references.
- The issue has been reproduced using:
- Microsoft-hosted agents: ubuntu-latest and windows-latest
- Self-hosted agents on Windows
- Agent version used in all cases: 4.254.0
This behavior suggests a regression or limitation in the handling of multiple private GitHub repositories as artifacts in newly created release pipelines, or possibly a breaking change in how GitHub artifacts are retrieved in recent versions of the Azure DevOps agent or backend services.
We kindly ask the Azure DevOps support team to investigate this inconsistency and confirm:
• Is this a known issue or intentional limitation?
• Are there any workarounds (e.g. enforced usage of GitHub Releases, artifact proxying through build pipelines)?
• Will this be addressed in a future update?
Azure DevOps
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 28.999999999999996%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGK%3C/text%3E%3C/svg%3E)
Gaurav Kumar 305 Reputation points Microsoft External Staff2025-05-02T10:00:48.6933333+00:00 Hi @Nikolay Gurinov ,
Instead of adding the private GitHub repositories directly as artifacts in the release pipeline, separate Build pipeline for each GitHub repository.
Each build pipeline simply checks out the repo and publishes it as an internal Azure DevOps artifact.
Then in the Release pipeline, use the internal build artifacts instead of connecting to GitHub directly.Pipeline for Private GitHub Repo:
trigger: - main pool: vmImage: 'ubuntu-latest' resources: repositories: - repository: self type: github endpoint: github-private-conn name: OrgName/repoA steps: - checkout: self - task: PublishBuildArtifacts@1 inputs: pathToPublish: '$(Build.SourcesDirectory)' artifactName: 'RepoA'Change the repo name and artifact name accordingly.
Let me know if you need any further assistance in the comments.
-
Nikolay Gurinov 0 Reputation points
2025-05-02T11:12:01.93+00:00 Hi,
Thanks for your reply. However, if you read my original message carefully, I was specifically referring to Release pipelines, not Build pipelines.
The issue occurs when trying to add multiple private GitHub repositories directly as artifacts in a Release pipeline — something that has worked reliably in the past and still works for previously created pipelines.
While the suggested workaround (using separate Build pipelines to publish artifacts) is valid and known, the point of this issue is to highlight a regression or limitation that affects Release pipelines using multiple private GitHub repositories directly as artifacts.
This behavior breaks previously supported functionality and complicates scenarios where Build pipelines are not necessary or desired.
Looking forward to further clarification or confirmation whether this is an intended change or a bug.
Thanks!
Sign in to comment
Sign in to answer