java.lang.RuntimeException: java.lang.NumberFormatException: For input string: ""

Jenkins JIRA | Stefan Drissen | 1 year ago
  1. 0

    Since installing the TFS plug-in 4.0.0 one of the slaves often fails with FATAL: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" {noformat} Started by upstream project "7.12/build work" build number 475 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on <machine> (oe11.4 oe10.2b) in workspace d:\jenkins\workspace\7.12\work\build_bl-11.4-oe FATAL: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:193) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:189) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:205) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:262) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:211) at hudson.model.AbstractProject.checkout(AbstractProject.java:1277) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Caused by: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source) at java.lang.Double.parseDouble(Unknown Source) at java.text.DigitList.getDouble(Unknown Source) at java.text.DecimalFormat.parse(Unknown Source) at java.text.SimpleDateFormat.subParse(Unknown Source) at java.text.SimpleDateFormat.parse(Unknown Source) at java.text.DateFormat.parse(Unknown Source) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parseExtended(LenientDateTimeParser.java:295) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parse(LenientDateTimeParser.java:380) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.DateVersionSpec.<init>(DateVersionSpec.java:59) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.VersionSpec.parseSingleVersionFromSpec(VersionSpec.java:230) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:59) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:33) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ......remote call to <machine>-50(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:778) at hudson.plugins.tfs.model.Server.execute(Server.java:106) ... 13 more {noformat} A build around the same time on the same slave did not fail: {noformat} Started by upstream project "7.12/build work" build number 475 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on <machine> (oe11.4 oe10.2b) in workspace d:\jenkins\workspace\7.12\work\build_ws-11.4 Querying for remote changeset at '$/<product>/7.12/work' as of 'D2015-09-10T08:10:36Z'... Query result is: Changeset #208683 by '<domain>\<user>' on '2015-09-10T08:08:46Z'. {noformat} Both these builds were started in parallel. It would seem that querying for remote changeset is sometimes failing to format the datetime correctly? Update. Just had one of a parallel pair complain - the invalid input string is identical to the previous fatal: {noformat} Started by upstream project "7.12/build work" build number 483 originally caused by: Started by user <user> [EnvInject] - Loading node environment variables. Building remotely on <machine> (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.12\work\build_bl-11.4-oe FATAL: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" at hudson.plugins.tfs.model.Server.execute(Server.java:110) {noformat} {noformat} Started by upstream project "7.12/build work" build number 483 originally caused by: Started by user <user> [EnvInject] - Loading node environment variables. Building remotely on <machine> (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.12\work\build_ws-11.4 Querying for remote changeset at '$/<product>/7.12/work' as of 'D2015-09-11T20:53:17Z'... Query result is: Changeset #208741 by '<domain>\<user>' on '2015-09-11T10:42:18Z'. {noformat} Update 2015-09-13: and another one of a parallel pair complained - the difference with the previous results is that the input string is empty: Successful start: {noformat} Started by upstream project "7.20/build work" build number 28 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on <machine-50> (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.20\work\build_bp-11.4 Querying for remote changeset at '$/<product>/7.20/work' as of 'D2015-09-13T20:02:26Z'... {noformat} Failed start: {noformat} Started by upstream project "7.20/build work" build number 28 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on <machine-50> (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.20\work\build_bl-11.4-oracle FATAL: java.lang.NumberFormatException: For input string: "" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "" at hudson.plugins.tfs.model.Server.execute(Server.java:110) {noformat} Update 2015-09-14: something else came in throwing the datetime handler in a new way: {noformat} Building remotely on <machine>-50 (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.20\work\build_ws-11.4 FATAL: java.lang.ArrayIndexOutOfBoundsException: -1 java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException: -1 at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:193) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:189) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:205) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:262) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:211) at hudson.model.AbstractProject.checkout(AbstractProject.java:1277) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at java.text.DigitList.fitsIntoLong(Unknown Source) at java.text.DecimalFormat.parse(Unknown Source) at java.text.SimpleDateFormat.subParse(Unknown Source) at java.text.SimpleDateFormat.parse(Unknown Source) at java.text.DateFormat.parse(Unknown Source) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parseExtended(LenientDateTimeParser.java:295) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parse(LenientDateTimeParser.java:380) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.DateVersionSpec.<init>(DateVersionSpec.java:59) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.VersionSpec.parseSingleVersionFromSpec(VersionSpec.java:230) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:59) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:33) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:69) at java.lang.Thread.run(Unknown Source) at ......remote call to <machine>-50(Native Method) {noformat} Update 2015-09-16 - now a build being performed on the master (with a slave orchestrating the multijob build) is failing: {noformat} Started by upstream project "7.20/build work" build number 52 originally caused by: Started by user <user> [EnvInject] - Loading node environment variables. Building on master in workspace C:\Program Files (x86)\Jenkins\jobs\7.20\jobs\work\jobs\build_ws-11.4\workspace FATAL: java.lang.NumberFormatException: For input string: "E.420155" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "E.420155" {noformat}

    Jenkins JIRA | 1 year ago | Stefan Drissen
    java.lang.RuntimeException: java.lang.NumberFormatException: For input string: ""
  2. 0

    [JENKINS-30382] TFS plug-in 4.0.0 NumberFormatExceptions - Jenkins JIRA

    jenkins-ci.org | 4 months ago
    java.lang.RuntimeException: java.lang.NumberFormatException: For input string: ""
  3. 0

    Since installing the TFS plug-in 4.0.0 one of the slaves often fails with FATAL: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" {noformat} Started by upstream project "7.12/build work" build number 475 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on <machine> (oe11.4 oe10.2b) in workspace d:\jenkins\workspace\7.12\work\build_bl-11.4-oe FATAL: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:193) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:189) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:205) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:262) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:211) at hudson.model.AbstractProject.checkout(AbstractProject.java:1277) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Caused by: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source) at java.lang.Double.parseDouble(Unknown Source) at java.text.DigitList.getDouble(Unknown Source) at java.text.DecimalFormat.parse(Unknown Source) at java.text.SimpleDateFormat.subParse(Unknown Source) at java.text.SimpleDateFormat.parse(Unknown Source) at java.text.DateFormat.parse(Unknown Source) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parseExtended(LenientDateTimeParser.java:295) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parse(LenientDateTimeParser.java:380) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.DateVersionSpec.<init>(DateVersionSpec.java:59) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.VersionSpec.parseSingleVersionFromSpec(VersionSpec.java:230) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:59) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:33) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Unknown Source) at ......remote call to <machine>-50(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:778) at hudson.plugins.tfs.model.Server.execute(Server.java:106) ... 13 more {noformat} A build around the same time on the same slave did not fail: {noformat} Started by upstream project "7.12/build work" build number 475 originally caused by: Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on <machine> (oe11.4 oe10.2b) in workspace d:\jenkins\workspace\7.12\work\build_ws-11.4 Querying for remote changeset at '$/<product>/7.12/work' as of 'D2015-09-10T08:10:36Z'... Query result is: Changeset #208683 by '<domain>\<user>' on '2015-09-10T08:08:46Z'. {noformat} Both these builds were started in parallel. It would seem that querying for remote changeset is sometimes failing to format the datetime correctly? Update. Just had one of a parallel pair complain - the invalid input string is identical to the previous fatal: {noformat} Started by upstream project "7.12/build work" build number 483 originally caused by: Started by user <user> [EnvInject] - Loading node environment variables. Building remotely on <machine> (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.12\work\build_bl-11.4-oe FATAL: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: ".2001155E4.2001155E4" at hudson.plugins.tfs.model.Server.execute(Server.java:110) {noformat} {noformat} Started by upstream project "7.12/build work" build number 483 originally caused by: Started by user <user> [EnvInject] - Loading node environment variables. Building remotely on <machine> (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.12\work\build_ws-11.4 Querying for remote changeset at '$/<product>/7.12/work' as of 'D2015-09-11T20:53:17Z'... Query result is: Changeset #208741 by '<domain>\<user>' on '2015-09-11T10:42:18Z'. {noformat} Update 2015-09-13: and another one of a parallel pair complained - the difference with the previous results is that the input string is empty: Successful start: {noformat} Started by upstream project "7.20/build work" build number 28 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on <machine-50> (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.20\work\build_bp-11.4 Querying for remote changeset at '$/<product>/7.20/work' as of 'D2015-09-13T20:02:26Z'... {noformat} Failed start: {noformat} Started by upstream project "7.20/build work" build number 28 originally caused by: Started by an SCM change Started by an SCM change Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on <machine-50> (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.20\work\build_bl-11.4-oracle FATAL: java.lang.NumberFormatException: For input string: "" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "" at hudson.plugins.tfs.model.Server.execute(Server.java:110) {noformat} Update 2015-09-14: something else came in throwing the datetime handler in a new way: {noformat} Building remotely on <machine>-50 (oe11.4 windows oe10.2b) in workspace d:\jenkins\workspace\7.20\work\build_ws-11.4 FATAL: java.lang.ArrayIndexOutOfBoundsException: -1 java.lang.RuntimeException: java.lang.ArrayIndexOutOfBoundsException: -1 at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:193) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:189) at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:205) at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:262) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:211) at hudson.model.AbstractProject.checkout(AbstractProject.java:1277) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:408) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at java.text.DigitList.fitsIntoLong(Unknown Source) at java.text.DecimalFormat.parse(Unknown Source) at java.text.SimpleDateFormat.subParse(Unknown Source) at java.text.SimpleDateFormat.parse(Unknown Source) at java.text.DateFormat.parse(Unknown Source) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parseExtended(LenientDateTimeParser.java:295) at com.microsoft.tfs.util.datetime.LenientDateTimeParser.parse(LenientDateTimeParser.java:380) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.DateVersionSpec.<init>(DateVersionSpec.java:59) at com.microsoft.tfs.core.clients.versioncontrol.specs.version.VersionSpec.parseSingleVersionFromSpec(VersionSpec.java:230) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:59) at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:33) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:69) at java.lang.Thread.run(Unknown Source) at ......remote call to <machine>-50(Native Method) {noformat} Update 2015-09-16 - now a build being performed on the master (with a slave orchestrating the multijob build) is failing: {noformat} Started by upstream project "7.20/build work" build number 52 originally caused by: Started by user <user> [EnvInject] - Loading node environment variables. Building on master in workspace C:\Program Files (x86)\Jenkins\jobs\7.20\jobs\work\jobs\build_ws-11.4\workspace FATAL: java.lang.NumberFormatException: For input string: "E.420155" java.lang.RuntimeException: java.lang.NumberFormatException: For input string: "E.420155" {noformat}

    Jenkins JIRA | 1 year ago | Stefan Drissen
    java.lang.RuntimeException: java.lang.NumberFormatException: For input string: ""
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Before upgrading to 4.0.0 I was using this plugin to get the code/apply a label to a branch based on the job parameter, so in my setup I have: Server = http://myserver:8080/tfs/TFS2010 Project Path = $/{color:red}*${Branch}*{color}/DMSP/Request Administration Where {color:red}*${Branch}*{color} is the branch name, populated from a "Choice Parameter". After I installed the new version, I noticed that applying label is no longer working, my label name is: "RequestAdministration-${AppVersion}" But once the job runs its trying to apply the label to ${Branch} and not to the real branch name: Creating label 'RequestAdministration-4.2.0.7' on '$/${Branch}/DMSP/Request Administration' as of the current version in workspace 'Hudson-RequestAdministration-MASTER'... ERROR: Build step failed with exception java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again. at hudson.plugins.tfs.model.Server.execute(Server.java:110) On the version 3.2 its works great: [RequestAdministration] $ "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\tf.exe" label RequestAdministration-4.2.0.8 . -version:WHudson-RequestAdministration-MASTER -comment:Automatically_applied_by_Jenkins_TFS_plugin -noprompt -recursive -server:http://myserver:8080/tfs/TFS2010 ******** Thanks! Full error is below: Creating label 'RequestAdministration-4.2.0.7' on '$/${Branch}/DMSP/Request Administration' as of the current version in workspace 'Hudson-RequestAdministration-MASTER'... ERROR: Build step failed with exception java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again. at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.TFSLabeler.perform(TFSLabeler.java:85) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1769) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: com.microsoft.tfs.core.exceptions.TECoreException: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again. at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:105) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:50) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.labelItem(WebServiceLayer.java:1282) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayerLocalWorkspaces.labelItem(WebServiceLayerLocalWorkspaces.java:909) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createLabel(VersionControlClient.java:5057) at hudson.plugins.tfs.model.MockableVersionControlClient.createLabel(MockableVersionControlClient.java:48) at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:67) at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:22) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:106) ... 10 more Caused by: com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again. at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:132) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:1103) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:732) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:475) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.labelItem(_RepositorySoap12Service.java:889) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.labelItem(WebServiceLayer.java:1267) ... 17 more Build step 'Create a label in TFS' marked build as failure

    Jenkins JIRA | 1 year ago | guilherme labigalini
    java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again.
  6. 0

    Before upgrading to 4.0.0 I was using this plugin to get the code/apply a label to a branch based on the job parameter, so in my setup I have: Server = http://myserver:8080/tfs/TFS2010 Project Path = $/{color:red}*${Branch}*{color}/DMSP/Request Administration Where {color:red}*${Branch}*{color} is the branch name, populated from a "Choice Parameter". After I installed the new version, I noticed that applying label is no longer working, my label name is: "RequestAdministration-${AppVersion}" But once the job runs its trying to apply the label to ${Branch} and not to the real branch name: Creating label 'RequestAdministration-4.2.0.7' on '$/${Branch}/DMSP/Request Administration' as of the current version in workspace 'Hudson-RequestAdministration-MASTER'... ERROR: Build step failed with exception java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again. at hudson.plugins.tfs.model.Server.execute(Server.java:110) On the version 3.2 its works great: [RequestAdministration] $ "C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\tf.exe" label RequestAdministration-4.2.0.8 . -version:WHudson-RequestAdministration-MASTER -comment:Automatically_applied_by_Jenkins_TFS_plugin -noprompt -recursive -server:http://myserver:8080/tfs/TFS2010 ******** Thanks! Full error is below: Creating label 'RequestAdministration-4.2.0.7' on '$/${Branch}/DMSP/Request Administration' as of the current version in workspace 'Hudson-RequestAdministration-MASTER'... ERROR: Build step failed with exception java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again. at hudson.plugins.tfs.model.Server.execute(Server.java:110) at hudson.plugins.tfs.TFSLabeler.perform(TFSLabeler.java:85) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1769) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: com.microsoft.tfs.core.exceptions.TECoreException: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again. at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:105) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:50) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.labelItem(WebServiceLayer.java:1282) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayerLocalWorkspaces.labelItem(WebServiceLayerLocalWorkspaces.java:909) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createLabel(VersionControlClient.java:5057) at hudson.plugins.tfs.model.MockableVersionControlClient.createLabel(MockableVersionControlClient.java:48) at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:67) at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:22) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:106) ... 10 more Caused by: com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again. at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:132) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:1103) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:732) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:475) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.labelItem(_RepositorySoap12Service.java:889) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.labelItem(WebServiceLayer.java:1267) ... 17 more Build step 'Create a label in TFS' marked build as failure

    Jenkins JIRA | 1 year ago | guilherme labigalini
    java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: TF10122: The path '$/${Branch}/DMSP/Request Administration' contains a '$' at the beginning of a path component. Remove the '$' and try again.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.RuntimeException

      java.lang.NumberFormatException: For input string: ""

      at hudson.plugins.tfs.model.Server.execute()
    2. hudson.plugins.tfs
      Server.execute
      1. hudson.plugins.tfs.model.Server.execute(Server.java:110)
      1 frame