docker-smoke: add build-only mode#9
Merged
Conversation
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.
Why
Some apps can't boot a working container in CI without runtime secrets or a database (e.g. ecm: reads
ACTIONKIT_*atcreate_app()and starts a scheduler against a live DB). For those, the full run+probe smoke isn't feasible, but building the image at PR time is still valuable — it catches Dockerfile / base-image breaks (the corepack class) that today only surface in the post-merge release.What
Adds a
build-onlyinput (defaultfalse). Whentrue, the action builds the image and stops — the run, probe, and teardown steps are skipped viaif:guards. Default behaviour is unchanged (full build + run + Host-header probe).Usage