Buildkite

Hybrid CI/CD platform where build agents run on your own infrastructure (any cloud, on-prem, macOS, Windows, ARM) while Buildkite Cloud handles orchestration, pipeline UI, and artifact storage coordination. Pipelines defined as YAML (steps, parallel groups, block steps, wait steps) or generated dynamically at runtime. Plugin ecosystem for Docker, Kubernetes, test analytics, and more. Confidence is docs-derived.

REST API: /v2/organizations/{org}/pipelines for pipeline CRUD; /v2/organizations/{org}/builds for build list/trigger; /v2/organizations/{org}/builds/{id} for build status and logs; GraphQL API for complex queries; Webhook events (build.started, job.finished, etc.) for downstream triggers; Buildkite Agent REST API on localhost for artifact upload, annotation, and metadata within jobs.

Organization-level API token with scoped permissions (read_builds, write_builds, read_pipelines, etc.); per-pipeline agent token for agent registration (not user credentials); SSO/SAML for team access; secrets injected via environment variables or Buildkite Secrets (Elastic CI Stack); agent token is separate from API token — principle of least privilege; audit log for all API operations.

Build queue and agent dispatch are asynchronous; job status returned via polling or webhook; parallel step groups auto-distribute jobs across available agents; dynamic pipeline upload (buildkite-agent pipeline upload) enables programmatic step generation at runtime; retry configuration per step with manual or automatic retry policies; REST API returns structured JSON with error codes on failure.

Documentation covers agent installation (Docker, Kubernetes, macOS, Windows), YAML pipeline reference, dynamic pipeline generation, plugin authoring, REST and GraphQL API reference, test analytics setup, and Elastic CI Stack for AWS. Comprehensive tutorial library. Enterprise-grade with strong team adoption. Confidence is docs-derived.