search

jenkinsci / conventional-commits-plugin

This plugin can be used to determine the next release version based on previous tags and the commit messages used.
https://plugins.jenkins.io/conventional-commits/
MIT License
23 stars 33 forks source link

nextVersion: Unexpected character #293

Open kobmik opened 1 year ago

kobmik commented 1 year ago

Jenkins and plugins versions report

Environment ```text Paste the output here ```

What Operating System are you using (both controller, and any agents involved in the problem)?

Linux

Reproduction steps

We would like to use nextVersion() in a Jenkins pipeline to generate the next semantic version. The plugin can read the current tag but fails to generate the next version.

Expected Results

return the next version

Actual Results

Also: org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 9c419606-6cbd-430f-ae09-f66bb71a5bf2 Unexpected character 'ILLEGAL([)' at position '0', expecting '[DIGIT]' at com.github.zafarkhaja.semver.VersionParser.consumeNextCharacter(VersionParser.java:516) at com.github.zafarkhaja.semver.VersionParser.digits(VersionParser.java:448) at com.github.zafarkhaja.semver.VersionParser.numericIdentifier(VersionParser.java:408) at com.github.zafarkhaja.semver.VersionParser.parseVersionCore(VersionParser.java:285) at com.github.zafarkhaja.semver.VersionParser.parseValidSemVer(VersionParser.java:255) at com.github.zafarkhaja.semver.VersionParser.parseValidSemVer(VersionParser.java:195) at com.github.zafarkhaja.semver.Version.valueOf(Version.java:265) ...

Anything else?

No response

hepifish commented 11 months ago

same here..

anvi-27 commented 1 month ago

The gitag accepted seems to be only of type digits; the git tag must be in the format of only number with no prefix. Accepted: 1.0.0 Not accepted: v1.0.0, [1.0.0]