Build and publish boost devnet containers via CI #1661
Merged
Conversation
This file contains 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
masih
force-pushed
the
masih/build-boost-containers
branch
3 times, most recently
from
414efd6
to
973123f
Compare
Build boost containers on each PR to assert that all containers used by devnet build. On non PR events publish the containers onto ghcr.io. This should significantly reduce wait time when interacting with devnet for well known versions of boost since a user would no longer have to build all related images from scratch. The CI is setup to use GitHub actions caching layers which should further speed up builds per commit. The containers built will have a tag prefix that corresponds to the target name of devnet dockerfile.source. This includes: * `boost-dev` * `booster-http-dev` * `booster-bitswap-dev` * `lotus-dev` * `lotus-miner-dev`
masih
force-pushed
the
masih/build-boost-containers
branch
from
c6dc36b
to
a7fa60b
Compare
masih
changed the title
willscott
approved these changes
Sep 1, 2023
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.
Build boost containers on each PR to assert that all containers used by devnet build. On non PR events publish the containers onto ghcr.io.
This should significantly reduce wait time when interacting with devnet for well known versions of boost since a user would no longer have to build all related images from scratch. The CI is setup to use GitHub actions caching layers which should further speed up builds per commit.
The containers built will have a tag prefix that corresponds to the target name of devnet dockerfile.source. This includes:
boost-devbooster-http-devbooster-bitswap-devlotus-devlotus-miner-dev