I am very glad to discover this plugin as it make build info really helpful at first sight. I use
#${BUILD_NUMBER}: ${GIT_REVISION,length=8} (${GIT_BRANCH}) by ${BUILD_USER_ID}
It seems that this plugin make build unstable as Jenkins build often fails over IllegalStateException (Build step 'Changes build name' marked build as failure), while actual build is SUCCESS
Reproduction steps
Step 1...
Step 2...
It is hard to reproduce exactly, but I noticed that manually started build (not scmChange) are usually successful.
Results
Expected result:
BUILD successfull
Actual result:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:04 min
....
[JENKINS] Archiving /hbdata/data/jenkins_data/workspace/...-1.0.0-SNAPSHOT.jar
channel stopped
ERROR: Build step failed with exception
java.lang.IllegalStateException
at org.objectweb.asm.tree.analysis.BasicInterpreter.<init>(BasicInterpreter.java:66)
at org.parboiled.transform.RuleMethodInterpreter.<init>(RuleMethodInterpreter.java:42)
at org.parboiled.transform.InstructionGraphCreator.process(InstructionGraphCreator.java:41)
at org.parboiled.transform.ParserTransformer.runMethodTransformers(ParserTransformer.java:62)
at org.parboiled.transform.ParserTransformer.extendParserClass(ParserTransformer.java:45)
at org.parboiled.transform.ParserTransformer.transformParser(ParserTransformer.java:39)
at org.parboiled.Parboiled.createParser(Parboiled.java:54)
Caused: java.lang.RuntimeException: Error creating extended parser class: null
at org.parboiled.Parboiled.createParser(Parboiled.java:58)
at org.jenkinsci.plugins.tokenmacro.Parser.process(Parser.java:80)
at org.jenkinsci.plugins.tokenmacro.Parser.process(Parser.java:74)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:199)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:237)
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:207)
at org.jenkinsci.plugins.buildnamesetter.Executor.evaluateMacro(Executor.java:75)
at org.jenkinsci.plugins.buildnamesetter.Executor.setName(Executor.java:30)
at org.jenkinsci.plugins.pipeline.BuildNameStep.perform(BuildNameStep.java:35)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:80)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:803)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:944)
at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:894)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:513)
at hudson.model.Run.execute(Run.java:1906)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Build step 'Changes build name' marked build as failure
Collecting metadata...
Metadata collection done.
13-04-2021 23:02:43 Allure Report Recorder Plugin: job class name:MavenModuleSetBuild
13-04-2021 23:02:43 Allure Report Recorder Plugin: job type invalid,not analyse
Finished: FAILURE
I am very glad to discover this plugin as it make build info really helpful at first sight. I use
It seems that this plugin make build unstable as Jenkins build often fails over
IllegalStateException
(Build step 'Changes build name' marked build as failure), while actual build is SUCCESSReproduction steps
Results
Expected result:
BUILD successfull
Actual result:
Version report
Jenkins and plugins versions report:
build-name-setter:2.1.0