merrily01 opened a new pull request, #1213:
URL: https://github.com/apache/auron/pull/1213
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #1212 .
# Rationale for this change
This PR unifies the build process for the Auron project by consolidating
both local and Docker-based build logic into a single entrypoint script:
`auron-build.sh`.
Previously, local builds were triggered via `auron-build.sh`, while Docker
builds required a separate `release-docker.sh` wrapper. This separation caused
redundancy and increased maintenance burden. With this update, Docker builds
are fully supported within `auron-build.sh` via a new `--docker` flag.
# What changes are included in this PR?
- Added `--docker true|false` flag to `auron-build.sh` (default: `false`);
- All build arguments (`--sparkver`, `--scalaver`, `--uniffle`, `--javaver`,
`--skiptests`, etc.) are now supported uniformly;
- The script parses all arguments locally, constructs the full auton build
command, and executes it either directly or inside
Docker;
- Docker Compose is used to mount volumes and run the build with provided
`AURON_BUILD_ARGS`;
- Deprecated and removed `release-docker.sh`;
- Simplified `docker-compose.yml` to only execute the passed-in build args.
# Are there any user-facing changes?
Yes.
`auron-build.sh` now supports `--docker` for Docker-based builds, and
`release-docker.sh` has been removed.
All builds are now handled through auron-build.sh, for example:
* Local build:
```
./auron-build.sh --release --sparkver 3.5 --scalaver 2.12 --javaver 11
```
* Docker build:
```
./auron-build.sh --docker true --release --sparkver 3.5 --scalaver 2.12
--uniffle 0.9
```
# How was this patch tested?
Manually tested in both local and Docker modes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
