Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Default Artifact Feed Permssions on Azure DevOps not sufficient for publish command #35

Open
batesbw opened this issue Sep 21, 2022 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@batesbw
Copy link

batesbw commented Sep 21, 2022

By default, the "Build Service" user only gets "Collaborator" role when a new Artifact feed is created in Azure DevOps. This role is insufficient for publishing artifacts. At minimum, the "Contributor" role is required to publish Artifacts.

Steps to replicate:

Expected Results:

  • Artifacts are published to appropriate Feed

Actual Results:

  • Pipeline fails at "Publish artifacts to NPM registry" stage.

Can the documentation be updated to include the following steps prior to running the "Quick Build Deploy" pipeline:

  • Click the "Settings" icon of Artifact Feed
  • Click the "Permissions" tab
  • Check the Role of the Build Service user. The format of the user name is [Project Name] Build Service ([org name]) e.g. "My DevOps Project Build Service (mydevopsorg)"
  • If the role is "Reader" or "Collaborator", click the "Add users/groups" button
  • Find the Build Service user and update the Role to "Contributor"
  • Click "Save"
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants