ci(docker): add build cache for antithesis local pipeline#3063
Draft
shuowang12 wants to merge 1 commit intomainfrom
Draft
ci(docker): add build cache for antithesis local pipeline#3063shuowang12 wants to merge 1 commit intomainfrom
shuowang12 wants to merge 1 commit intomainfrom
Conversation
shuowang12
force-pushed
the
shuo/antithesis-local-pipeline-build-cache
branch
from
953b120 to
0670946
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.
Description
Add cache mounts to the walrus-antithesis image build so that running the antithesis pipeline locally (
docker/walrus-antithesis/build-test-config-image/pipeline.sh) does incremental rebuilds instead of a fullcargo buildevery time. This is helpful for verifying changes to antithesis test quickly.Test plan
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that
a user might notice and any actions they must take to implement updates. (Add release notes after the colon for each item)