[Buildbot] Add Buildbot build status badge#11938
Conversation
|
|
Hello @LuxologyGG 👋🏻 What are the API rate limits? |
Same answer, the Buildbot REST API rate limits depend on the self-hosted instance. Since this targets user-hosted servers, there's no universal limit. Happy to add a note in the docs about it |
fb7c2f8 to
157724f
Compare
|
The Buildbot REST API documentation does not document request rate limits. Buildbot is self-hosted, so any throttling is configured by the operator (for example via a reverse proxy in front of the web server; see the Web Server configuration docs). This badge issues one GET request per badge render to I have also fixed the ESLint failures ( |
Implement badge for issue badges#6837 using the Buildbot REST API to show the latest build result for a builder.
c7437c6 to
048a798
Compare
Closes #6837
Summary
Adds a new Buildbot build status badge that queries a self-hosted Buildbot instance's REST API for the latest build result on a given builder.
Example
Changes
services/buildbot/buildbot.service.js— fetches{baseUrl}/api/v2/builders/{builder}/builds?limit=1&order=-numberand maps Buildbot result codes to badge statusservices/buildbot/buildbot.service.spec.js— unit tests for URL building, result transformation, and renderingservices/buildbot/buildbot.tester.js— live and mocked integration testsAPI rate limits
The Buildbot REST API documentation does not define request rate limits. Buildbot is self-hosted, so any throttling is configured by the operator (for example via a reverse proxy). This badge issues a single GET per request with
limit=1.Review feedback addressed
no-unused-vars,sort-class-members, Prettier)masterChecklist
services/buildbot/buildbot.service.js)services/buildbot/buildbot.service.spec.js)services/buildbot/buildbot.tester.js)npm run test:core -- --grep Buildbot(15 passing)npm run test:services -- --grep Buildbot(3 passing)npm run lint(0 errors)