CODEWITHSUNDEEP
azureazure-devopsazure-pipelinesdevopsazure-pipelines-release-pipeline
Bere
Bere

Reputation: 46

Azure DevOps Release Pipelines permission

I have two projects in my Azure DevOps environment. Project H and Project HB. Project H contains the Board of Tasks and Repo for source code. Project HB contains the build and release pipelines. The build works as it shoud, as does the release pipeline. But I get an error in the "Release" view, when looking at the Commits made for the release.

TF401019: The Git repository with name or identifier '' does not exist or you do not have permissions for the operation you are attempting.

enter image description here

Which permissions should I configure to get the release to be able to show the commits and Work Items related to the release?

Is it possible to report the deployment status back to boards that exists in another project?

I Tried to add Read permission to the repo and boards in "Project H" for the account "Project HB Build Service".

Upvotes: 1

Views: 1148

Answers (1)

promicro
promicro

Reputation: 1646

1

We have the same problem with the Stakeholder access. Team members can open the page in your screenshot, but stakeholder have the issue as described by you.

So, it's not about the Build Service access, but the user who opens the release status should have access to Project HB.

If the user already has access, then this might be a limitations within the classic release overview.

2

Two answer the second part, you should however see the build status, of the yaml pipeline, in the work items of project H. The deploy status, of classic release pipelines, is a different story. AFAIK it's only reported back to the project it is in.

Maybe publishing a deployment badge can help you: classic release integration options

3

Alternatively you could migrate to YAML pipelines, since reporting back of these pipelines have more options then the classic release pipelines.

Upvotes: 1

Related Questions