Replies: 1 comment 2 replies
-
thanks for reaching out! it's incredibly difficult for us to be able to do much in the way of debugging/troubleshooting private self-hosted instances, and all I can tell you definitively is that badge message is indicative of the Azure DevOps API returning a 404 response. You may want to try hitting the upstream endpoint directly (either in your web browser or with a client like curl) with the exact same values you are providing for the badge route parameters: https://dev.azure.com/${organization}/${projectId}/_apis/build/status/${definitionId} e.g. https://dev.azure.com/swellaby/opensource/_apis/build/status/25 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to use shields.io on a private azure devops repo.
I have setup shields locally via docker(using the following guideline: https://github.com/badges/shields/blob/master/doc/self-hosting.md#docker) and I have set the AZURE_DEVOPS_TOKEN environment variabile with my PAT.
Unfortunately, when I try to generate the repo's build badge, a badge with the following error message is generated: "user or project not found"
This is the shield's url I'm using to generate the repo's build badge:
http://localhost:8080/azure-devops/build/[organization]/[project id]/[definition id]
Beta Was this translation helpful? Give feedback.
All reactions