ci: publish Boost 1.91 builder base image - #132
Merged
Conversation
Noble ships Boost 1.83. Building 1.90 in a separate rarely-rebuilt image keeps the Boost compile out of per-PR builds, so warm CI stays at today's 4-6 min. Verified locally: the image builds in ~7.5 min, installs 20 static Boost libs and BoostConfig.cmake, and the project configures inside it against 1.90.0.
The CI Docker Hub account can push tags to repos that already exist but cannot create a new vizblockchain/boost repo (push denied, insufficient_scope). Store the base image as vizblockchain/vizd:boost-base-1.90-noble instead, which needs no repo creation.
chiliec
force-pushed
the
ci/boost-base-image
branch
from
August 5, 2026 02:32
1e47991 to
8f69864
Compare
chiliec
force-pushed
the
ci/boost-base-image
branch
from
August 5, 2026 04:30
8e4e3b7 to
aefcec9
Compare
chiliec
changed the title
On1x
approved these changes
Aug 5, 2026
On1x
left a comment
On1x
left a comment
Member
There was a problem hiding this comment.
Reviewed. Base-image plumbing (Dockerfile-boost + boost-base-image.yml) is clean: the temporary ci/boost-base-image publish trigger was already dropped (36a027e), so the workflow publishes only on master pushes touching those two paths; tag is boost-base-1.91-noble, byte-identical to the copy in #131. Image is published and live on Docker Hub. CI green. LGTM.
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.
Publish the Boost 1.91 builder base image
Adds the prebuilt Boost 1.91 builder image plumbing, split out so it can land independently of the migration (#131).
share/vizd/docker/Dockerfile-boost— builds Boost 1.91 on Noble (static libs +BoostConfig.cmake), ~7.5 min. The compiledsystemlibrary is not built: 1.91 dropped the stub (Boost.System is header-only since 1.69) andb2errors on it as an unknown--with-librariesname..github/workflows/boost-base-image.yml— builds and pushes the base image. Triggers onworkflow_dispatchor a push tomastertouching either file.Where the image is published
The base image is stored as a tag on the existing
vizblockchain/vizdrepo:vizblockchain/vizd:boost-base-1.91-noble. The CI Docker Hub account can push tags to repos that already exist but cannot create a new repo (vizblockchain/boost→push access denied, insufficient_scope), so a dedicated repo isn't an option without an org-side grant. The tag is already published and live. If a dedicatedvizblockchain/boostrepo is provisioned later, flip the tag reference here and in #131.Status
The temporary publish trigger (which listed
ci/boost-base-imageunderpush:so the image could be built before merge) has been removed — the workflow now publishes only on pushes tomaster. This branch is clean to merge.