This plugin provides opinions and tasks for the release process provided by gradle-git.
If you want the release plugin to trigger or finalize a publishing task you will need to configure it:
tasks.release.dependsOn tasks.<publish task name>
-or-
tasks.release.finalizedBy tasks.<publish task name>
This plugin also detects the presence of the nebula-bintray-plugin
and wires itself to depend on the task types used by bintrayUpload and artifactoryUpload.
Project using this plugin will use semantic versions style strings. e.g. major.minor.patch-<prerelease>+<metadata>
All tasks default to bumping the minor version.
nebulaRelease {
Set<String> releaseBranchPatterns = [/master/, /HEAD/, /main/, /(release(-|\/))?\d+(\.\d+)?\.x/, /v?\d+\.\d+\.\d+/] as Set
Set<String> excludeBranchPatterns = [] as Set
String shortenedBranchPattern = /(?:(?:bugfix|feature|hotfix|release)(?:-|\/))?(.+)/
void addReleaseBranchPattern(String pattern)
void addExcludeBranchPattern(String pattern)
}
| Property | Type | Default | Description |
|---|---|---|---|
| releaseBranchPatterns | Set<String> |
[master, HEAD, main, (release(-|\/))?\d+(\.\d+)?\.x, v?\d+\.\d+\.\d+] |
Branch patterns that are acceptable to release from. The default pattern will match things like master, 1.2.x, release-42.x, release/2.x, v1.2.3. If the set is empty releases will be possible from any branch that doesn't match excludeBranchPatterns. |
| excludeBranchPatterns | Set<String> |
[] |
Branch patterns that you cannot release from. If a branch matches both releaseBranchPatterns and excludeBranchPatterns it will be excluded. |
| shortenedBranchPattern | String |
(?:(?:bugfix|feature|hotfix|release)(?:-|\/))?(.+) |
Branch widget1 will append widget1 to snapshot version numbers, and branch (feature|bugfix|release|hotfix)/widget2 will append widget2 to snapshot version numbers. You may configure this field, the regex is expected to have exactly one capture group. |
| Method | Arguments | Description |
|---|---|---|
| addReleaseBranchPattern | String pattern |
Calling this method will add a pattern to the set of releaseBranchPatterns, usage: nebulaRelease { addReleaseBranchPattern(/myregex/) |
| addExcludeBranchPattern | String pattern |
Calling this method will add a pattern to the set of excludeBranchPatterns, usage: nebulaRelease { addExcludeBranchPattern(/myregex/) |
All tasks will trigger gradle-git's release task which is configured to depend on the build task if the project produces JVM based jar or war artifacts.
- final - Sets the version to the appropriate
<major>.<minor>.<patch>, creates tagv<major>.<minor>.<patch> - candidate - Sets the version to the appropriate
<major>.<minor>.<patch>-rc.#, creates tagv<major>.<minor>.<patch>-rc.#where#is the number of release candidates for this version produced so far. 1st 1.0.0 will be 1.0.0-rc.1, 2nd 1.0.0-rc.2 and so on. - devSnapshot - Sets the version to the appropriate
<major>.<minor>.<patch>-dev.#+<hash>, does not create a tag. Where#is the number of commits since the last release andhashis the git hash of the current commit. If releasing a devSnapshot from a branch not listed in thereleaseBranchPatternsand not excluded byexcludeBranchPatternsthe version will be<major>.<minor>.<patch>-dev.#+<branchname>.<hash>- You can use
nebula.release.features.replaceDevWithImmutableSnapshot=truein yourgradle.propertiesfile to change pattern of version to<major>.<minor>.<patch>-snapshot.<timestamp>+<hash>. Wheretimestampis UTC time inYYYYMMddHHmmformat, ex.201907052105andhashis the git hash of the current commit. If releasing a immutableSnapshot from a branch not listed in thereleaseBranchPatternsand not excluded byexcludeBranchPatternsthe version will be<major>.<minor>.<patch>-snapshot.<timestamp>+<branchname>.<hash>
- You can use
- snapshot - Sets the version to the appropriate
<major>.<minor>.<patch>-SNAPSHOT, does not create a tag.
Use of devSnapshot vs snapshot is a project by project choice of whether you want maven style versioning (snapshot) or semantic versioned snapshots (devSnapshot).
We attempt to pick up on the fact that you're on certain release branches.
Examples:
- On release/1.x - The plugin will default to versioning you 1.0.0-SNAPSHOT
- On 3.x - The plugin will default to versioning you 3.0.0-SNAPSHOT
- On 4.2.x - The plugin will default to versioning you 4.2.0-SNAPSHOT
There are many cases where a project may want to bump a part of the version string besides the minor number.
- bump the major number:
./gradlew <snapshot|devSnapshot|candidate|final> -Prelease.scope=major - bump the patch number:
./gradlew <snapshot|devSnapshot|candidate|final> -Prelease.scope=patch
In the scenario, where the tag is already created but you want to go through the release process, you can use the "Last Tag Strategy". When enabled, the plugin will respect the last tag as the version. This works well in a CI environment where a user will tag the code, and CI is configured to do just the release upon finding a new tag. The tag names need to follow the versioning scheme, e.g. "v1.0.1". To enact, provide the release.useLastTag project property, e.g.
git tag v1.0.0
./gradlew -Prelease.useLastTag=true final
To set the version from the command line, set the release.version system property:
./gradlew -Prelease.version=1.2.3 final
If this is the first time releasing with this plugin and you've released in the past you may need to create a tag in your repository. You should find the hash of your latest release and create a tag of the format v<major>.<minor>.<patch> e.g. v1.4.2. For example, if the hash of your last release was da5d4f9:
git tag v1.4.2 da5d4f9
git push --tags
./gradlew final
This will create a tag v<string> where String is whatever you set on release.version. If you want the plugin to work from here on out you should choose a version that matches semantic versioning described above.
./gradlew -Prelease.version=42.5.0 final
The plugin assumes Git root is in the same location as Gradle root. If this isn't the case, you may specify a different path for Git root via the git.root Gradle property. For example:
./gradlew -Pgit.root=<git root path> final
Historically, this plugin generated versions using build metadata which comes after the + sign. While we suggest using this approach to be semver compliant, some people has raised their need for removing the build medata and make it part of the pre-release string.
For this, starting on version 11.0.0 we have introduced a sanitizeVersion flag. Ex.
./gradlew -Prelease.sanitizeVersion=true devSnapshot
This will generate a version string similar to: 0.1.0-dev.2.e1c43c7
Please note that now the build metadata is part of the pre-release information and could affect how versions are handled by a SemVer library/tool.
devSnapshotSetup- any kind of setup is good to live around here, e.g. setting status, various checksrelease- probably havereleasedependOn anyassembleandchecktasks, dependsOndevSnapshotSetuppostRelease- any steps you want to happen after the repo tag, in our case this is where publishing happens since if the publish partially fails we don't want to fix the tags, dependsOnreleasedevSnapshot- command line task to kick off devSnapshot workflow, dependsOnpostRelease
snapshotSetup- any kind of setup is good to live around here, e.g. setting status, various checksrelease- probably havereleasedependOn anyassembleandchecktasks, dependsOnsnapshotSetuppostRelease- any steps you want to happen after the repo tag, in our case this is where publishing happens since if the publish partially fails we don't want to fix the tags, dependsOnreleasesnapshot- command line task to kick off snapshot workflow, dependsOnpostRelease
candidateSetup- any kind of setup is good to live around here, e.g. setting status, various checksrelease- this is where the tag is pushed to the repo, so probably havereleasedependOn anyassembleandchecktasks, dependsOncandidateSetuppostRelease- any steps you want to happen after the repo tag, in our case this is where publishing happens since if the publish partially fails we don't want to fix the tags, dependsOnreleasecandidate- command line task to kick off candidate workflow, dependsOnpostRelease
finalSetup- any kind of setup is good to live around here, e.g. setting status, various checksrelease- this is where the tag is pushed to the repo, so probably havereleasedependOn anyassembleandchecktasks, dependsOnfinalSetuppostRelease- any steps you want to happen after the repo tag, in our case this is where publishing happens since if the publish partially fails we don't want to fix the tags, dependsOnreleasefinal- command line task to kick off final workflow, dependsOnpostRelease
Built with OpenJDK8 Tested with OpenJDK8
| Gradle Version | Works |
|---|---|
| 5.0 | yes |
| 5.1 | yes |
| 5.2 | yes |
| 5.3 | yes |
| 5.4 | yes |
| 5.5 | yes |
Copyright 2014-2019 Netflix, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent