Skip to content

buildkite: publish a deployctl bundle for each build - #41

Open
NullHypothesis wants to merge 3 commits into
v1.14.4-flyfrom
deployctl-bundle-v1.14.4
Open

NullHypothesis wants to merge 3 commits into
v1.14.4-flyfrom
deployctl-bundle-v1.14.4

Conversation

@NullHypothesis

Copy link
Copy Markdown

fcm-layers will soon install Firecracker with deployctl, which reads s3://flyio-builds/firecracker/<branch>/<commit>.tar.gz and <branch>/HEAD. Publish that next to the existing loose binaries, which hosts on older fcm-layers still read. The bundle holds root-owned bin/firecracker and bin/jailer; HEAD moves only after the bundle is uploaded.

fcm-layers installs Firecracker with deployctl, which reads
s3://flyio-builds/firecracker/<branch>/<commit>.tar.gz and <branch>/HEAD.
Publish that next to the existing loose binaries, which hosts on older
fcm-layers still read. The bundle holds root-owned bin/firecracker and
bin/jailer; HEAD moves only after the bundle is uploaded.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@NullHypothesis
NullHypothesis requested a review from a team as a code owner November 10, 2026 19:08
philipp-fly and others added 2 commits November 12, 2026 16:37
fcm-layers writes each channel's version into flyd's config, which
decides which Firecracker features flyd configures. Ship it as VERSION,
taken from the built binary, so the config can't disagree with the pin.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
YAML folds each block back into one line, so the commands Buildkite
runs are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants