nebula-release-plugin icon indicating copy to clipboard operation
nebula-release-plugin copied to clipboard

Release opinions based around gradle-git

Results 58 nebula-release-plugin issues
Sort by recently updated
recently updated
newest added

Is there any way to dynamically set some other version despite having some other in git flow? Example: I have a GIT flow which had tags in master: v1.1.0.3 v1.1.0.2...

Hello, today happened that two builds has been triggered simultaneously. Unfortunately the build for older commit won the battle and successfully pushed a tag the second one build for older...

Consider the following config: ``` nebulaRelease { shortenedBranchPattern = /(?:(?:bug|chore|feature|refactor|release)(?:-|\/))?(\d+)/ } ``` With that config, version evaluation will fail from any branch that doesn't match that pattern (i.e. doesn't start...

If a project is following, http://keepachangelog.com/en/1.0.0/, it's easier to determine automatically which part of the version needs to be incremented. The plugin can even update `CHANGELOG.md` itself.

Should work through plugin workflow and call devSnapshot, snapshot, candidate, final

(I'm on Ubuntu 14.04) I have multiple private keys in my ~/.ssh folder, but also one with the default name (id_rsa). When running ./gradlew prepare, gnome-keyring asks for the password...

enhancement

Run through more test cases to discover edge cases. including but not limited to: - Releasing from a tag that is not at head - Checking that the commit the...

enhancement

happening on version 19.0.6 ## Current behaviour If the push of the release tag fails, the build continues uninterrupted. ## Expected behaviour If the push of the release tag fails,...

`./gradlew clean` FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring project ':account-inquiry-starter'. > Could not determine the dependencies of null. > Could not resolve...

The code [here](https://github.com/nebula-plugins/nebula-release-plugin/blob/main/src/main/groovy/nebula/plugin/release/ReleaseExtension.groovy#L19C17-L19C38) defines a set of regular expressions for patterns that should match any branch from which releases should be permitted. Among this default set I would recommend adding...