nebula-release-plugin
nebula-release-plugin copied to clipboard
nebula-plugins
Release opinions based around gradle-git
Split it into BRANCH_METADATA_STRATEGY and COMMIT_ABBREVIATED_ID to make it easier to compose and customise. Handle case of a branch matching `releaseBranchPatterns` as a no-op. Avoid crash if branch doesn't match...
in NetflixOSSStrategies would it be possible to add this logic? ` String shortenedBranch = "" try { shortenedBranch = (state.currentBranch.name =~ nebulaReleaseExtension.shortenedBranchPattern)[0][1] } catch (Exception ignored) { // no match...
When using TagStrategy setPrefixNameWithV(false) the full contents of the Git history is contained in every release notes section. This is because the TagStrategy generateMessage closure grabs the "previousVersion" and always...
Just like maven's release plugin and another commonly used gradle release plugin (https://github.com/researchgate/gradle-release), can we support optionally adding a release commit and post-release commit?
As far as I understood the plugin will use semantic versioned snapshots versions by default (e.g. for build), but a maven style snapshot can by published by running the `snapshot`...
If I create a multiproject-build structure from scratch with gradle 7.3 and I apply the "nebula.release" plugin in a build.gradle file that is NOT located in the root folder I...
If gralde.properties contains git.root=.. and the jvm running gradle then Grgit calculates the relative directory against the gradle daemon's working directory not the project. This doesn't happen when running java...
I'm trying to use the Nebula release plugin with a Scala plugin and I noticed something that I can't explain. I created a very simple Gradle (6.6) build with the...
I was (unfortunately) able to invoke the following command: `./gradlew clean snapshot -Prelease.version="2.7.1"` which led to tagging my repo with sort of 'final' version tag despite the fact that the...
