Scale-Out Delivery Platform→
Complexity is inevitable. Tame it and gain your competitive advantage.
Capabilities
Pipelines→
Build the CI/CD workflows you need.
Test Engine→
Remove flaky tests, split tests, optimize performance.
Package Registries→
Speed up builds, lock down security.
Mobile Delivery Cloud→
Supercharge your mobile app delivery.
Bring your own compute
Self-hosted agents Self-hosted Kubernetes Self-hosted AWS Self-hosted Google Cloud
Hosted compute
Mac hosted agents Linux hosted agents
Replace Jenkins
Shift your software delivery into high gear.
Workflows for AI/ML
Tame the chaos of model delivery today to prepare for 10× tomorrow.
Testing at scale
Deliver quickly and confidently, at any scale.
Monorepo mojo
Scale your monorepo without scaling your problems.
Bazel orchestration
Unlock full-speed Bazel with dynamic pipelines and unlimited scale.
Example pipelines
Browse a collection of quick-start pipeline examples.
Webinars
Register for upcoming sessions or watch on-demand recordings.
Blog
Insights from the team building Buildkite.
Public pipelines
See public and open source projects powered by Buildkite.
Case studies
Real-world customer success stories.
Events
Join us at industry conferences and community meetups.
Changelog Plugins Migration Services Newsletter
Follow Buildkite

About

The company behind Scale-Out Software Delivery.

Careers

Join the team!

pipeline.yaml

name: "Join Buildkite"
description: "Fetch all jobs, filter by relevance, and apply"
steps:
  - command: "curl -X GET 'https://boards-api.greenhouse.io/v1/boards/buildkite/jobs' \ -H 'Content-Type: application/json' \ -v"
    label: ":terminal: Fetch latest jobs"

Press and news Legal Security Brand assets

Follow Buildkite

Resources
/
Examples
/
Deploy Confirmation Block Step

Buildkite Deploy Confirmation Block Step Example

This repository is an example Buildkite pipeline that shows how to use a block step to confirm deployments - but only if the date command on the agent returns Friday.

See the full Getting Started Guide for step-by-step instructions on how to get this running.

How it works

If the current day is Friday, a block step will appear asking for manual deploy confirmation. The user can choose to:

✅ Confirm deploy Respond: "Yes, I'm sure. If something goes wrong, I'll fix it" → deploy.sh runs normally
❌ Cancel deploy Respond: "Err, nah. I've changed my mind" → deploy.sh still runs but exits with a failure