Skip to content

[P2-018] Run batch files in the build slot by full path - #4

Merged
deku2026 merged 1 commit into
mainfrom
p2-018-build-slot-batch
Sep 25, 2026
Merged

deku2026 merged 1 commit into
mainfrom
p2-018-build-slot-batch

Conversation

@deku2026

Copy link
Copy Markdown

Follow-up to #3. The first real build through build-slot run failed with "'gradlew.bat' is not recognized". This workstation sets NoDefaultCurrentDirectoryInExePath=1, so cmd.exe does not search the current directory, and the documented -- cmd /c gradlew.bat build example cannot work.

  • build-slot run now runs a .bat or .cmd command from the current directory through cmd /c by its full path.
  • arcforges-implementation.md documents -- gradlew.bat build.
  • The offline build-slot test covers a batch file named without a path (exit code propagated).

Validation: python -m unittest discover -s tools/tests, run through the build slot, passed all 17 tests.

🤖 Generated with Claude Code

The first real build through `build-slot run` failed with "'gradlew.bat'
is not recognized": this workstation sets NoDefaultCurrentDirectoryInExePath,
so cmd.exe does not search the current directory, and the documented
`-- cmd /c gradlew.bat` example cannot work. build-slot run now runs a
.bat/.cmd command from the current directory through cmd /c by its full
path, and the procedure documents `-- gradlew.bat build`. The offline
build-slot test covers a batch file named without a path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@deku2026
deku2026 merged commit c2dddaf into main Sep 25, 2026
@deku2026
deku2026 deleted the p2-018-build-slot-batch branch September 26, 2026 06:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant