Repository navigation
feat(crossbind)!: choose the runner in the system config - #215
Merged
bugra9 merged 1 commit intoOct 7, 2026
Merged
Conversation
RUNNER in ~/.crossbind.json decides where every toolchain step runs, and CROSSBIND_RUNNER overrides it. REMOTE joins DOCKER_RUN, DOCKER_EXEC and LOCAL: each image's steps go to the runner at REMOTE_URL_<IMAGE>, or REMOTE_URL for every image, keys that CROSSBIND_REMOTE_URL[_<IMAGE>] override, while tokens stay in the environment. An address alone no longer sends a step anywhere, a step whose image has no address stops before anything runs instead of falling back to the local Docker, and each image says once which runner its steps go to. utils/selectRunner.js resolves the runner for run.js, cargo and conan alike. An invalid RUNNER stops the first step that needs it, so `crossbind config set` can still repair it. `runner start` and `runner init` print the config commands that point builds at a runner. ADR-0015 records the decision. BREAKING CHANGE: a host wasi-sdk (WASI_SDK_PATH, CROSSBIND_WASI_SDK_PATH) applies under RUNNER=LOCAL only; with the other runners a wasi build uses the sdk in the image, as CI does. Build on the host with CROSSBIND_RUNNER=LOCAL.
bugra9
deleted the
feat/crossbind/choose-the-runner-in-the-system-config
branch
October 7, 2026 20:04
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.
Summary
RUNNERin~/.crossbind.jsondecides where every toolchain step runs;CROSSBIND_RUNNERoverrides it for CI and single builds.REMOTEsends each image's steps to the runner atREMOTE_URL_<IMAGE>(orREMOTE_URL); tokens stay inCROSSBIND_TOKEN[_<IMAGE>].REMOTE, a step whose image has no address stops with an error naming the setting instead of falling back to the local Docker.utils/selectRunner.jsresolves the runner forrun.js, cargo and conan;runner startandrunner initprintcrossbind config setcommands. ADR-0015 records the decision.Breaking change
WASI_SDK_PATHandCROSSBIND_WASI_SDK_PATHapply underRUNNER=LOCALonly; the other runners build wasi with the sdk in the image, as CI does. Host build:CROSSBIND_RUNNER=LOCAL crossbind build -p wasi.Test plan
pnpm --filter crossbind test: 1275 passed, 1 skipped; also withCROSSBIND_RUNNERand runner addresses exportedpnpm run lint,pnpm check:agents,pnpm test:site,pnpm --filter @crossbind/landing buildports/zlibend to end with a throwawayHOME: an address alone stayed in Docker; a missing address stopped with 0 docker calls; an invalidRUNNERfailed the build andcrossbind config setrepaired itRUNNER=REMOTEagainst a local runner: 0 docker calls, 37 files byte-identical to local Docker (run before the missing-address change)