Repository navigation
ci: migrate overlay builds and artifact smoke to Buildkite - #28
Merged
Merged
Conversation
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
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.
Move BCR checks, commit hooks, optimized cross-builds and Linux/macOS artifact smoke to Buildkite. Windows GNU artifacts run on the existing Windows queue; MSVC remains on GHA. Linux ARM64 native coverage stays on GHA. Replace yanked libaio
.bcr.0with.bcr.1in development/consumer harnesses; published overlay entries remain unchanged.One producer builds distribution assets; smoke jobs verify commit, build, pipeline and SHA-256 before running them. Fork commits require approval except verified Renovate. Bazel caches use the existing pipeline/branch-isolated
oss-ci-v2registry.Trusted tag builds stage assets on GitHub using short-lived workflow tokens. GHA verifies those assets, runs ARM64 artifact smoke and publishes without rebuilding. Release Please and BCR submission wait for the exact main Buildkite status. Existing release/BCR secrets stay on GHA.
Validation: official Buildkite schema, actionlint, shell syntax, overlay metadata, eight artifact security tests and ten release gate tests passed. Existing OSS queues and GitHub trigger/fork/tag/token settings configured. Automatic PR synchronize triggers verified. Buildkite build 2 passed at
edec007316, including both BCR suites and Linux/macOS/Windows artifact smoke. Retained ARM64 GHA passed; MSVC coverage remains enabled. Real tag upload/publishing awaits the next release.