ci(release): run binary + docker builds on Blacksmith#9
Merged
Conversation
Scoped replacement for #8. Only `tero-release.yaml` is touched — the upstream-Vector CI workflows stay on standard runners so future syncs don't conflict on every file. Heavy compile jobs get the bigger runner; docker assembly stays on 4vcpu. - build-binary matrix: blacksmith-8vcpu-ubuntu-2404 / -arm - build-docker matrix: blacksmith-4vcpu-ubuntu-2404 / -arm - merge-docker-manifest: blacksmith-4vcpu-ubuntu-2404 - docker/setup-buildx-action -> useblacksmith/setup-docker-builder - docker/build-push-action -> useblacksmith/build-push-action (drops manual cache-from/to: type=gha; Blacksmith's colocated layer cache is handled by the builder automatically) Untouched: prepare, upload-release-assets, summary — they don't build anything, so they stay on ubuntu-24.04. actions/cache@v4 is also left alone; it auto-interacts with Blacksmith's cache backend when the job runs on a Blacksmith runner.
jaronoff97
added
the
no-changelog
smithclay
approved these changes
Jun 1, 2026
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.
Summary
Scoped replacement for #8 — only the binary + Docker build jobs in
tero-release.yamlmove to Blacksmith. The 36 other workflow files (upstream-Vector CI, cla/static-analysis/etc.) are left on standard GitHub runners so they don't conflict on every upstream sync.Changes
.github/workflows/tero-release.yaml:ubuntu-24.04→blacksmith-8vcpu-ubuntu-2404arm-4-core→blacksmith-8vcpu-ubuntu-2404-armubuntu-24.04→blacksmith-4vcpu-ubuntu-2404ubuntu-24.04-arm→blacksmith-4vcpu-ubuntu-2404-armblacksmith-4vcpu-ubuntu-2404docker/setup-buildx-action@v3→useblacksmith/setup-docker-builder@v1docker/build-push-action@v6→useblacksmith/build-push-action@v2cache-from: type=gha/cache-to: type=gha,mode=max— Blacksmith's setup-docker-builder wires the colocated layer cache automatically.Untouched (intentionally — these don't build anything, no reason to spend Blacksmith on them):
prepare,upload-release-assets,summary.actions/cache@v4(cargo registry/build cache) is also left as-is; per Blacksmith's docs, official GitHub cache actions automatically use the colocated cache backend when the job runs on a Blacksmith runner.Change Type
Is this a breaking change?