0

My build failed as described in this post however unlike aforementioned, Project Collection Build Service was already marked as Contributor. I solved the issue by checking "Allow project-scoped builds". This added another user named [Project name] Build Service.

Shouldn't the Project Collection Build Service permission allow me to create the build? I don't understand why I have to set Allow project-scoped builds for each project. I'm going to forget this and I will need to look it up again when the build fails on my next project.

1 Answers1

0

By default, the Project Collection Build Service is a Contributor. If you've changed your builds to run at project scope, you'll need to add the project-level build identity as a Reader or Contributor.

You could check the Pipeline settings under your Azure DevOps Organization settings:

  • If Limit job authorization scope to current project for non-release pipelines is enabled, then the scope is project.
  • If Limit job authorization scope to current project for non-release pipelines is not enabled, then check the Pipeline settings under your Project settings in Azure DevOps:
    • If Limit job authorization scope to current project for non-release pipelines is enabled, then the scope is project.
    • Otherwise, the scope is collection.
Cece Dong - MSFT
  • 29,631
  • 1
  • 24
  • 39