badges/shields

Azure DevOps - Build Badge - PAT Token not used on private projects

Open

#10162 opened on May 10, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (22,337 stars) (5,423 forks)batch import
good first issueservice-badge

Description

Are you experiencing an issue with...

My own instance of shields

🐞 Description

Our organisation has strict rules on access, as such anonymous access to badges is disabled.

I have configured PAT token and other Azure DevOps badges work great, the build badges however do not use the PAT token as part of the requests, as such are not able to access the projects.

🔗 Link to the badge

https://shields.io/badges/azure-dev-ops-builds-branch https://shields.io/badges/azure-dev-ops-builds

💡 Possible Solution

Implement fetch using auth (if PAT provided) as other Azure DevOps badges do.

Contributor guide

Tech stack
javascriptnodejsazurerest api
Domain
backendapidevops
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Node.jsHTTP requests
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine how other Azure DevOps badges (e.g., test results) implement authentication using PAT token. Look at the Azure DevOps build badge service file (likely in services/azure devops/azure devops build.service.js) and modify the request to include the auth token from the configuration. Ensure existing tests pass and add a test if necessary.