Repository navigation
fix(runner): pass JIT config through runner environment - #2
Merged
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
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
The runner now starts successfully with GitHub's current JIT contract: the one-time config reaches
run.shthroughACTIONS_RUNNER_INPUT_JITCONFIGinstead of being passed to the unsupportedconfig.sh --jitconfigCLI. The wrapper removesIMP_GITHUB_JITCONFIGbeforerun.sh, keeps the payload out of argv/logs, and the focused smoke assertion covers the handoff and secret-safety guarantees.Verification
shellcheck -x build-runner-layer.sh build.sh smoke.sh runner-layer/runnerRUNNER_VERSION=2.337.0 RUNNER_ARCH=x64 ./build-runner-layer.shBASE_IMAGE=imp-runner-base-test:jit-fix RUNNER_IMAGE=imp-runner-layer-test:jit-fix ./smoke.sh/usr/local/bin/runnerfrom the built runner image and verified it matchesrunner-layer/runnerbyte-for-byteThe publish workflow will build and publish immutable SHA-tagged images on the release/tag path; this PR does not deploy or publish an image.