CODEWITHSUNDEEP
azure-devopsazure-pipelines
Ree5un
Ree5un

Reputation: 197

VSO Build -- Response status code does not indicate success: 404 (Not Found)

Build always fails upon attempt to SYNC, Response status code does not indicate success: 404 (Not Found)

Repository Type is GIT, deployed an agent in local machine,

Build Definition:

Upvotes: 2

Views: 8067

Answers (2)

gregsonian
gregsonian

Reputation: 1226

One additional thing I discovered is Stakeholders cannot access the repos, even if they have Reader or Contributor access by being part of the team. Access levels are controlled at the TFS configuration level under the Access Control tab. Simply remove them from the Stakeholders group and add them to the Basic (default) group, or some other more-specific group you have created.

Upvotes: 2

Eddie Chen - MSFT
Eddie Chen - MSFT

Reputation: 29976

Please check if "Project Collection Build Service" has "Read" permission to your code repository via following steps:

  1. Open your project from Web Portal.
  2. Click "Code" to open code panel.
  3. Right click on the repository and select "Security" option.
  4. Check the permission of "Project Collection Build Service". enter image description here

Make sure "Read" permission is set to "Allow", otherwise you will get a 404 error as following: enter image description here

Upvotes: 3

Related Questions