docs: add a Buildkite build server page - #3426
Open
NickJosevski wants to merge 1 commit into
Open
Conversation
getting-started lists BuildKite among the CI systems we provide guides for, but no such page exists — build-servers documents nine other systems and not this one. Buildkite users have had nothing to follow. Covers what was verified end to end against a Buildkite hosted agent and an Octopus Cloud instance: installing the CLI (it is not preinstalled on Buildkite agents), the OpenID Connect token exchange, the create-release plugin, and the traps. The most important of those is the subject claim. Buildkite's includes the commit SHA, so a subject copied from one build authorises only that build and then silently never matches again. The page calls that out in a warning with the wildcard form. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Pull request environment is available at https://stoctodocspr3426.z22.web.core.windows.net. You can view the ephemeral environment status in Octopus Deploy. This environment will be automatically deprovisioned when the pull request is closed, or after 7 days of inactivity. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
getting-started/index.mdxlists BuildKite among the CI systems we "provide first-class integrations with" and give guides for. There is no such page —build-servers/documents nine other systems and not this one. Buildkite users following that promise land nowhere.What's in it
Everything here was verified end to end against a Buildkite hosted agent and an Octopus Cloud instance, not inferred from the API:
install-octopus-cli. The page gives the tarball recipe that was actually used.create-releaseplugin or the CLI directly.The bit I'd most want reviewed
Buildkite's subject claim pins the commit SHA:
So a subject copied verbatim from a working build authorises exactly that build and then silently never matches again — with an error that gives no hint which half is wrong.
commit:*is effectively mandatory. That's in a warning callout, and it's the single thing most likely to cost a customer an afternoon.It's also the strongest argument for eventually giving Buildkite a guided issuer type in the portal like GitHub Actions has, rather than leaving people to hand-write a five-segment subject in a free-text field.
Also
build-servers/index.md(alphabetical,navOrder: 45between BitBucket Pipelines and Codefresh)./docs/...links verified to resolve to real pages.Known gaps this page documents rather than fixes
No login plugin, no build-information plugin, no CLI-install plugin for Buildkite. The page tells the truth about each rather than omitting them.
🤖 Generated with Claude Code