###Gradle Release Plugin
Gradle plugin that helps with SCM and release management for Performance Tools modules.
Execute ./gradlew verifyLicensing to scan dependencies and verify if all the licenses are valid.
SCM is an ultimate source of truth about project version and you will not find it hardcoded in the source code.
To get the current version of the project from Git execute ./gradlew currentVersion.
To release a new version of a module that uses the plugin execute ./gradlew release.
You should release new version only from master branch.
We use gradle signing plugin to sign our releases.
Follow instructions from the plugin's documentation to provide your key information.
You can use either gradle.properties or environment variables
signing.keyId=24875D73
signing.password=secret
signing.secretKeyRingFile=/Users/me/.gnupg/secring.gpg
In order to attempt to publish a new version to all configured repositories, execute ./gradlew publish.
Some repositories forbid publishing SNAPSHOT versions in order to serve only stable and tested artifacts.
If you want to perform integration test with your SNAPSHOT version, you can ./gradlew publishToMavenLocal.
If you wish to mark a new major / minor version simply execute ./gradlew markNextVersion -Prelease.version=**version**.
For example to start a new version 0.2.0 execute ./gradlew markNextVersion -Prelease.version=0.2.0.
For more information please refer to axion-release-plugin docs and Maven Publish Plugin docs
The plugin automatically configures Atlassian maven-central repository.
The credentials are read from atlassian_private_username and atlassian_private_password env
variables with a fallback to Maven settings.xml file.
If you don't have the credentials, the plugin will not configure them,
so you can still use the repo anonymously, e.g. for read access.
We track all the changes in a public issue tracker. All the suggestions and bug reports are welcome.
See CONTRIBUTING.md.
Copyright (c) 2018 Atlassian and others. Apache 2.0 licensed, see LICENSE.txt file.