ci: skip redundant Docker builds in CI#158
Closed
jakebromberg wants to merge 1 commit intotask/reduce-ci-minutesfrom
Closed
ci: skip redundant Docker builds in CI#158jakebromberg wants to merge 1 commit intotask/reduce-ci-minutesfrom
jakebromberg wants to merge 1 commit intotask/reduce-ci-minutesfrom
Conversation
In GitHub Actions, Docker images are already built by docker/build-push-action steps before ci-env.sh runs. The ci:build call in ci-env.sh rebuilds them from scratch, wasting ~2 minutes. Add a --skip-build flag to ci-env.sh and pass it from the workflow's "Set Up Test Environment" step. Local ci:testmock continues to work unchanged.
ad7d257 to
b7d973a
Compare
This was referenced Feb 15, 2026
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.
Summary
--skip-buildflag toscripts/ci-env.shto skipnpm run ci:buildwhen Docker images are already built--skip-buildfrom the workflow's "Set Up Test Environment" step, sincedocker/build-push-actionalready builds and tags the imagesnpm run ci:testmockcontinues to work unchanged (no flag passed)Estimated savings
~1-2 minutes per integration test run (eliminates redundant Docker image rebuilds)
Test plan
--skip-build(no Docker build output in "Set Up Test Environment" step)npm run ci:testmockstill builds images and runs tests correctly