[JIRA] (JENKINS-38677) Failure to create label in TFS

1 view
Skip to first unread message

andrew.paul.gray@gmail.com (JIRA)

unread,
Oct 4, 2016, 1:23:02 AM10/4/16
to jenkinsc...@googlegroups.com
Andrew Gray created an issue
 
Jenkins / Bug JENKINS-38677
Failure to create label in TFS
Issue Type: Bug Bug
Assignee: redsolo
Components: tfs-plugin
Created: 2016/Oct/04 5:22 AM
Environment: Windows 2012 Jenkins 2.24 tfs-plugin 5.2.1
Labels: tfs-plugin
Priority: Critical Critical
Reporter: Andrew Gray

Since upgrading to 5.2.1 of the TFS plugin bad things have started happening: Last step is to apply label to TFS if all unit tests pass. Instead I get this more often than not:

Creating label 'TPS_1927' on '$/PSD Team/TPS/TPS App' as of the current version in workspace 'Hudson-TPS-MASTER'...
ERROR: Build step failed with exception
java.lang.RuntimeException: java.lang.RuntimeException: Label creation failed.
at hudson.plugins.tfs.model.Server.execute(Server.java:226)
at hudson.plugins.tfs.TFSLabeler.perform(TFSLabeler.java:86)
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:720)
at hudson.model.Build$BuildExecution.post2(Build.java:185)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
at hudson.model.Run.execute(Run.java:1745)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: java.lang.RuntimeException: Label creation failed.
at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:70)
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:222)
... 10 more

This is REALLY BAD.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

andrew.paul.gray@gmail.com (JIRA)

unread,
Oct 4, 2016, 6:02:02 PM10/4/16
to jenkinsc...@googlegroups.com
Andrew Gray updated an issue
Change By: Andrew Gray
Since upgrading to 5.2.1 of the TFS plugin bad things have started happening:  Last step in job is to apply label to TFS if all unit tests pass.  Instead I get this more often than not:


Creating label 'TPS_1927' on '$/PSD Team/TPS/TPS App' as of the current version in workspace 'Hudson-TPS-MASTER'...
ERROR: Build step failed with exception
java.lang.RuntimeException: java.lang.RuntimeException: Label creation failed.
at hudson.plugins.tfs.model.Server.execute(Server.java:226)
at hudson.plugins.tfs.TFSLabeler.perform(TFSLabeler.java:86)
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:720)
at hudson.model.Build$BuildExecution.post2(Build.java:185)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
at hudson.model.Run.execute(Run.java:1745)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: java.lang.RuntimeException: Label creation failed.
at hudson.plugins.tfs.commands.LabelCommand.call(LabelCommand.java:70)
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:222)
... 10 more


This is REALLY BAD as we rely on labels to deploy by label via Web Deploy .

andrew.paul.gray@gmail.com (JIRA)

unread,
Oct 6, 2016, 8:09:03 PM10/6/16
to jenkinsc...@googlegroups.com
Andrew Gray commented on Bug JENKINS-38677
 
Re: Failure to create label in TFS

I will add that this error seems to occur in this corporate environment where it will intermittently effect builds for a couple of days at a time and then I'll get a sequence of days where the problem goes away completely only to return later.

Reply all
Reply to author
Forward
0 new messages