What’s new and updated in Buildkite
API updates and community releases
Posted March 29, 2016 by Tim
After a long weekend full of 🍫🐰 we’re happy to share some of the recent API updates that we’ve made based on your feedback 🛰️✨
Linkheader is now exposed via CORS headers so you can paginate API results in the browser.
- The Pipelines API now supports PATCH requests, allowing you to programatically update your build pipeline configuration.
- Pipeline response objects now include a
badge_urlproperty with the URL to its build badge.
- The build list APIs have a new
finishedbuild state alias, and you now can filter by multiple
- And finally, our GraphQL beta API has received lots of updates as we move more of our own frontend to be GraphQL powered 💪
In addition to the changes we’ve rolled out, here’s a few of the API integrations recently shared by the community:
- Boxkite was released by Matt Delves. Boxkite is an iOS app for managing your builds when you’re away from your computer, and makes use of almost every API we have available
- Buildkite AWS Cloudwatch Metrics Publisher received a big update thanks to Lachlan Donald from 99designs. The Cloudwatch Metrics Publisher monitors your build queues and publishes metrics to AWS Cloudwatch, so you can autoscale your build servers on demand
- terraform-buildkite was released by Martin Atkins at SayMedia, allowing you to setup and maintain your Buildkite account via Terraform, for all your meta-automation needs
- A Cog bundle for Buildkite was released by Operable, allowing you to query Buildkite pipelines via your ChatOps bot
- bk-board was released by Fraser Xu, a reporting dashboard for your Buildkite activity, and the accompanying buildkite-node npm library that powers it (via a lovely promises-based API)
- buildkite-git-trigger was released by timmipetit at Recras, allowing you to monitor arbitrary git repositories and trigger builds
If you’re using our API in interesting ways, or you find something missing that would help you, send a quick email to firstname.lastname@example.org—we’d love to hear from you ✉️
Happy building! 🎉