qcastel/Java Maven release
Release your Java application and publish artifacts
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| release-branch-name | Filter the branch to execute the release on | no | master |
| gpg-enabled | Enable gpg signing | no | false |
| gpg-key-id | The GPG key ID | no | — |
| gpg-key | The GPG key | no | — |
| gpg-passphrase | The GPG passphrase | no | — |
| ssh-private-key | The SSH private key used during the maven release git commit | no | — |
| ssh-passphrase | The SSH passphrase | no | — |
| ssh-extra-known-host | Additional SSH known host | no | — |
| ssh-ignore-default-hosts | Do not add the default SSH known hosts | no | — |
| git-release-bot-name | The git user name for committing the release | no | release-bot |
| git-release-bot-email | The git user email for committing the release | no | release-bot@github.com |
| git-skip-sanity-check | Skip the git fetch and reset executed for safety by this action | no | false |
| maven-repo-server-id | !!DEPRECATED: Use maven-servers instead!! Maven server repository id to push the artifacts to | no | "" |
| maven-repo-server-username | !!DEPRECATED: Use maven-servers instead!! Maven server repository username | no | "" |
| maven-repo-server-password | !!DEPRECATED: Use maven-servers instead!! Maven server repository password | no | "" |
| maven-servers | The maven server repositories, in a JSON format. Example: [{"id": "serverId1", "username": "username", "password": "password1", "privateKey": "privatekey1", "passphrase": "passphrase1"}, {"id": "serverId2", "username": "username2", "password": "password2"}] | no | [] |
| maven-args | The maven arguments for the release | no | "" |
| maven-project-folder | You may have more than one maven projects inside the repo. This option allows you to specify the folder for which you want to trigger the release | no | ./ |
| maven-options | The maven options for the release | no | "" |
| maven-development-version-number | If define, this option allows you to define a custom development version number, like ${parsedVersion.majorVersion}.${parsedVersion.nextMinorVersion}-SNAPSHOT | no | "" |
| maven-release-version-number | If define, this option allows you to define a custom release version number, like ${parsedVersion.majorVersion}.${parsedVersion.minorVersion}.0 | no | "" |
| docker-registry-id | The ID of your registry. For example, for docker hub, it is `registry.hub.docker.com` | yes | fake |
| docker-registry-username | The username for your docker registry | yes | fake |
| docker-registry-password | The password for your docker registry | yes | fake |
| skip-perform | Skip maven release perform | no | false |
| version-major | Increment the major version number | no | false |
| version-minor | Increment the minor version number | no | false |
| version-patch | Increment the patch version number <- By default, we will increase the patch version | no | false |
| m2-home-folder | M2 home folder | no | /root/.m2 |
| access-token | Github access token. https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line | no | — |
Outputs
no outputs