Buildkite is a joy for users and operators alike
What do you like best about the product?
Buildkite is a pleasure for our developers to use compared to other solutions we've tried. It is pluggable and customizable for the organization's needs without being cumbersome to customize. I love that we can use Vault to intuitively and securely store secrets for individual pipelines or shared secrets. We can encapsulate shared pipeline logic by writing simple plugins. Operating the runners is a breeze.
What do you dislike about the product?
Buildkite's documentation and tooling for plugins made it easy to fall into the trap of writing big plugins that are all bash code which is very difficult to test, so be mindful when writing plugins to only use bash as a minimal wrapper.
Their pipeline search functionality is not the greatest.
Onboarding pipelines is not the easiest, especially if you want the pipeline to be defined from code in the repo itself.
But these are small prices to pay for how great Buildkite is.
Their pipeline search functionality is not the greatest.
Onboarding pipelines is not the easiest, especially if you want the pipeline to be defined from code in the repo itself.
But these are small prices to pay for how great Buildkite is.
What problems is the product solving and how is that benefiting you?
Buildkite solves the business problem of securely deploying code into our infrastructure without being a pain to operate. Its usability also improves developers' engagement with their CI/CD processes, allowing them to tweak the process for increased speed and reliability. Buildkite is also used to automate everyday tasks we want non-SREs to feel comfortable initiating.