You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be much more helpful, if before applying incrementer.value.toString(), there would be a "null check" for the incrementer followed with proper error message stating:
"no matching branch specific incrementer was found for branch ${context.scmPosition.branch}"
(or something similar)
This would help understanding what is actually happening there.
I noticed the issue occurs more likely in case there is an existing version tag matching the current HEAD when running markNextVersion.
The text was updated successfully, but these errors were encountered:
Hi,
First of all, thanks for the work you're doing for this great plugin.
To provide some context:
I've tried to accomplish a release flow where:
I didn't find any predefined solutions to accomplish such versioning, so I started looking at 'branchSpecificIncrementer'.
Used plugin version:
The issue:
For some weird reason, even though I have a "default" (or "catch all") type of matcher as a last entry:
... running the
markNextVersion
task produces error:I followed the stack trace to notice the error is coming from NPE on
PredefinedVersionIncrementer.groovy
(line 60):To be expected:
It would be much more helpful, if before applying
incrementer.value.toString()
, there would be a "null check" for theincrementer
followed with proper error message stating:(or something similar)
This would help understanding what is actually happening there.
I noticed the issue occurs more likely in case there is an existing version tag matching the current
HEAD
when runningmarkNextVersion
.The text was updated successfully, but these errors were encountered: