jianguotian opened a new pull request, #11: URL: https://github.com/apache/paimon-full-text/pull/11
Purpose - Move Java RC staging deployment out of GitHub Actions so staging artifacts are deployed from a committer/RM machine. - Keep CI responsible for building and verifying release artifacts without using ASF Nexus or GPG deployment credentials. Changes - Replace the Java release workflow staging deploy job with a package verification job that builds the release profile with GPG disabled and uploads verified Java jars as workflow artifacts. - Keep native library builds in CI and upload the four platform-specific `native-*` artifacts for the RC run. - Add `tools/deploy_java_staging.sh` for committers to validate the RC tag, GitHub Actions run id, native artifacts, Maven outputs, and then deploy Java artifacts to Apache Nexus staging locally. - Add `tools/README.md` documenting prerequisites, the run-id source, parameters, dry-run flow, and real staging deploy flow. Tests - `bash -n tools/deploy_java_staging.sh` - `git diff --check` - Parsed all GitHub workflow YAML files with `yaml.safe_load`. - `python3 tools/validate_asf_yaml.py` (skipped because `.asf.yaml` is not present). - Ran targeted fake `gh`/fake `mvn` tests for missing `--run-id`, rejected `--native-dir`, dirty Java package inputs, wrong workflow, wrong event, mismatched run commit, deploy ordering, and temporary Maven settings XML escaping. - Ran a real Maven dry-run with fake GitHub artifacts: `mvn clean verify -Prelease -Dgpg.skip=true -DskipTests`. -- 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]
