-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
token-macro v1.11, build-name-setter v1.3, Jenkins v1.609.3
In some of our jobs, we use the build-name-setter plugin along with property files to set the name of the job based on values generated from the build. After upgrading to the latest version of the token-macro plugin, we are getting exceptions in the build. In our jobs, we have build-name-setter configured as follows:
<org.jenkinsci.plugins.buildnamesetter.BuildNameSetter plugin="build-name-setter@1.3"> <template>${PROPFILE,file="debian.properties",property="version"}</template> </org.jenkinsci.plugins.buildnamesetter.BuildNameSetter>
However, now when the build runs, we get the following exception:
00:00:39.540 FATAL: Remote call on USLOLBLDV80 failed 00:00:39.541 java.io.IOException: Remote call on USLOLBLDV80 failed 00:00:39.541 at hudson.remoting.Channel.call(Channel.java:786) 00:00:39.541 at hudson.FilePath.act(FilePath.java:1073) 00:00:39.541 at org.jenkinsci.plugins.tokenmacro.impl.PropertyFromFileMacro.evaluate(PropertyFromFileMacro.java:42) 00:00:39.541 at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:190) 00:00:39.541 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:190) 00:00:39.541 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:162) 00:00:39.541 at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.setDisplayName(BuildNameSetter.java:50) 00:00:39.541 at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter.access$000(BuildNameSetter.java:26) 00:00:39.541 at org.jenkinsci.plugins.buildnamesetter.BuildNameSetter$1.tearDown(BuildNameSetter.java:42) 00:00:39.541 at hudson.model.Build$BuildExecution.doRun(Build.java:171) 00:00:39.541 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) 00:00:39.541 at hudson.model.Run.execute(Run.java:1738) 00:00:39.541 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 00:00:39.541 at hudson.model.ResourceController.execute(ResourceController.java:98) 00:00:39.541 at hudson.model.Executor.run(Executor.java:381) 00:00:39.541 Caused by: java.lang.NoClassDefFoundError: java/nio/charset/StandardCharsets 00:00:39.541 at org.jenkinsci.plugins.tokenmacro.impl.PropertyFromFileMacro$ReadProperty.call(PropertyFromFileMacro.java:62) 00:00:39.541 at org.jenkinsci.plugins.tokenmacro.impl.PropertyFromFileMacro$ReadProperty.call(PropertyFromFileMacro.java:45) 00:00:39.541 at hudson.remoting.UserRequest.perform(UserRequest.java:121) 00:00:39.541 at hudson.remoting.UserRequest.perform(UserRequest.java:49) 00:00:39.541 at hudson.remoting.Request$2.run(Request.java:326) 00:00:39.541 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) 00:00:39.541 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 00:00:39.541 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 00:00:39.541 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) 00:00:39.541 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 00:00:39.541 at java.lang.Thread.run(Thread.java:701) 00:00:39.541 at ......remote call to USLOLBLDV80(Native Method) 00:00:39.541 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) 00:00:39.541 at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) 00:00:39.541 at hudson.remoting.Channel.call(Channel.java:778) 00:00:39.541 ... 14 more
If I roll back the plugin, everything works fine. (Also, it seems as though just PROPFILE is the only build-name-setter macro that is broken).
