Add cross-platform build scripts and update documentation for workflows#27
Conversation
… local build scripts
… workflows and local build scripts
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 238700f23f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| #!/bin/bash | ||
|
|
||
| # Navigate to the project root directory | ||
| cd "$(dirname "$0")/.." |
There was a problem hiding this comment.
Exit shell build script on first Gradle failure
The script never enables fail-fast mode (for example set -e), so if any ./gradlew ... step fails, execution continues to later steps and still prints a successful completion banner. In CI or other automation that invokes this script, a failing build/test can be reported as success because the script’s final exit status comes from the last echo command instead of the failed Gradle command.
Useful? React with 👍 / 👎.
| echo ====================================== | ||
|
|
||
| echo [1/6] Cleaning project... | ||
| call gradlew clean |
There was a problem hiding this comment.
Propagate Gradle failures in Windows build script
Each call gradlew ... invocation ignores %ERRORLEVEL%, so a failed Gradle task does not stop the script and it still reaches the success message (and pause) with a zero exit code. This can mask broken builds/tests in automated runs on Windows because callers cannot reliably detect task failure from the script result.
Useful? React with 👍 / 👎.
…APK/AAB artifacts to repository
No description provided.