CI: BuildKit remote bitstream builds (shared Makefile + reusable workflow)#2
Open
laktoosivaba wants to merge 1 commit into
Open
CI: BuildKit remote bitstream builds (shared Makefile + reusable workflow)#2laktoosivaba wants to merge 1 commit into
laktoosivaba wants to merge 1 commit into
Conversation
…low) Shared, reusable remote-build path: buildkitd on the build host reuses the mega base from its containerd store (no re-pull), runs Vivado in a Dockerfile RUN, exports a thin bitstream. ci/bitstream.mk (make bit / bit-push, vendored by projects), ci/Dockerfile.template, and a BuildKit reusable workflow (setup-buildx remote + build-push). Public repo: carries no infra defaults — projects pin BUILDKIT_ADDR / buildkit_endpoint / PUSH_REF themselves. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
laktoosivaba
force-pushed
the
ci/remote-bitstream
branch
from
July 5, 2026 14:13
429d8e1 to
5bddfba
Compare
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
1 participant
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.
Shared, reusable path to build FPGA bitstreams on a remote build host inside the mega image, driven from a laptop.
buildkitdon the build host reuses the mega base from its containerd store (no re-pull), runs Vivado in a DockerfileRUN, and exports a thin bitstream.ci/bitstream.mk—make bit/make bit-pushviabuildctlagainst a remote buildkitd. Projects include it and pin their ownBUILDKIT_ADDR(orBUILDKIT_HOST).ci/Dockerfile.template— multi-stageFROM mega → RUN vivado → FROM scratchartifact stage..github/workflows/vivado-bitstream.yml— reusable workflow (docker/setup-buildx-action@v4remote driver +docker/build-push-action@v7) for the same build, runnable viaact.No infrastructure defaults — projects pin
BUILDKIT_ADDR/buildkit_endpoint/PUSH_REF. Synthesis only; board programming stays in the consuming project.Verified end-to-end: a real Vivado bitstream (xc7z010) built on a remote buildkitd and exported locally, with the mega base reused from the host's containerd store (host disk flat — no re-pull).
🤖 Generated with Claude Code