Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buildkite badges #10369

Open
MichaelHinrichs opened this issue Jul 17, 2024 · 1 comment
Open

Buildkite badges #10369

MichaelHinrichs opened this issue Jul 17, 2024 · 1 comment
Labels
service-badge Accepted and actionable changes, features, and bugs

Comments

@MichaelHinrichs
Copy link

@MichaelHinrichs MichaelHinrichs added the service-badge Accepted and actionable changes, features, and bugs label Jul 17, 2024
@chris48s
Copy link
Member

Our existing BuildKite badge uses an unauthenticated and non-rate limited endpoint which just exposes one value

example call: https://badge.buildkite.com/3826789cf8890b426057e6fe1c4e683bdf04fa24d498885489.json

Moving to using the Rest API would require auth and also requires staying under a rate limit (200 requests per minute).

I suspect this one may also not be viable, but I think if someone is interested in working on this one, the first question to look into would be what data public data is available via the rest API. Does being an authenticated user allow access to any public metrics about all projects?

If not, do any of the documented scopes expose a small enough subset of data that they could be exposed in a badge URL? This probably need some input from someone who is at least a regular user of the BuildKite platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

No branches or pull requests

2 participants