Skip to content

Let the release workflow take extra Maven arguments - #2

Merged
venkata-kishore merged 1 commit into
primefrom
release-maven-args
Oct 29, 2026
Merged

venkata-kishore merged 1 commit into
primefrom
release-maven-args

Conversation

@venkata-kishore

Copy link
Copy Markdown
Member

Adds an optional maven-args input to maven-release.yml, matching the one maven-build.yml already has. A library whose tests need a service the runner lacks can then skip those tests when it releases, as well as when it builds.

  • The input defaults to empty, so existing callers behave exactly as before.
  • Its value goes into the publishing build, before the goals: ./mvnw ... -Ppublish ... $ARGS deploy [deploy:deploy ...]. It is passed through an environment variable, not interpolated into the script.
  • First user: the jedis fork, whose integration tests need a Redis server. It passes -DskipIntegrationTests=true to both workflows.
  • The README explains the input for both workflows. In maven-build.yml it replaces verify; in maven-release.yml it adds to the publishing build.

actionlint (with shellcheck) reports only the known ubuntu-26.04 label and the intentional word splitting of the Maven arguments.

@venkata-kishore
venkata-kishore merged commit 59f97a3 into prime Oct 29, 2026
1 check passed
@venkata-kishore
venkata-kishore deleted the release-maven-args branch October 29, 2026 04:12
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