nebula-release-plugin
nebula-release-plugin copied to clipboard
nebula-plugins
Release opinions based around gradle-git
I am currently working on externalizing common build steps of our projects (e.g. artefact publishing) using precompiled build scripts. In general this approach works fine but as soon as I...
`id 'nebula.release' version '15.0.0'` Error message does say ``` An exception occurred applying plugin request [id: 'java'] > Failed to apply plugin 'org.gradle.java'. > Could not create domain object 'test'...
``` id("nebula.release") version "17.1.0" ``` When trying the plugin to replace yet another git based versioning plugin I stumbled on this error: ``` * What went wrong: Failed to apply...
Nebula release plugin version `16.1.0`. Gradle version `7.5.1`. Our project is on branch `release/2.0.x`, branched from tag `v2.0.0`. When I run `./gradlew publish final` from my local machine I get:...
For example: 1. On Jenkins CI run for feature/branch-a, inferred version is 1.0.0-dev.30. 2. On Jenkins CI run for feature/branch-b, inferred version is 1.0.0-dev.31. 3. On Jenkins CI run for...
I’m currently using the Nebula Release Plugin and I noticed that it supports generating release candidates (rc). However, I couldn't find any documentation or configuration options to generate alpha or...
From version 18.0.6 and so on the NearestVersionLocator only read tags that use v as prefix, as you can see in this commit: https://github.com/nebula-plugins/nebula-release-plugin/commit/7d369f630fd937d7069e5c50857089e052ebf1e4 https://github.com/nebula-plugins/nebula-release-plugin/blame/c3850c0a954fafce9064c94ad1c47a58f94381fd/src/main/groovy/nebula/plugin/release/git/command/GitReadCommand.groovy#L115 But the base plugin gradle-git...
In my CI setup I run tests in a separate stage and only if they pass I'd want to run a task that sets the version and creates the tag....
