[JIRA] (JENKINS-36202) Listing tfs workspaces fails with 4.1.0
Title: Message Title Oleg N commented on JENKINS-36202 Re: Listing tfs workspaces fails with 4.1.0 This doesn't appear to be an issue with the TFS plug in, but I'm still not able to use the latest 4.1.0 version, only the 3.2 version. Our TFS server has been upgraded continuously since at least 2010 and there are some old workspaces in there whose guids are causing problems. If a query to TFS is sent without an owner (which becomes * in the console command) the same exception happens. What is the difference in calling the history commands in the plug in between the versions? Is it possible to make the current plug leave verbose information in the Jenkins console log? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36202) Listing tfs workspaces fails with 4.1.0
Title: Message Title Oleg N commented on JENKINS-36202 Re: Listing tfs workspaces fails with 4.1.0 Is there a way to see the exact command being called in the console log in the new 4.1.0 plugin, like it was possible in the 3.2 plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36202) Listing tfs workspaces fails with 4.1.0
Title: Message Title Oleg N created an issue Jenkins / JENKINS-36202 Listing tfs workspaces fails with 4.1.0 Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2016/Jun/23 5:30 PM Environment: Windows Server 2012, Jenkins 2.10, tfs-plugin 4.1.0, TFS Server 2015 update 2 Labels: plugin tfs-plugin tfs Priority: Minor Reporter: Oleg N I have full Visual Studio 2015 installed, to get its tf command, I had issues with TFS-CLC-14.0.3. When I try to connect to TFS in Jenkins with the 4.1.0 plug in, it fails like this: Listing workspaces from https://tfspro.x.net/tfs/TFS01... FATAL: com.microsoft.tfs.core.exceptions.TECoreException: TF14045: The identity b36238e8-6ac5-4f4a-bf3f-20005d3ed049 is not a recognized identity. java.lang.RuntimeException: com.microsoft.tfs.core.exceptions.TECoreException: TF14045: The identity b36238e8-6ac5-4f4a-bf3f-20005d3ed049 is not a recognized identity. When I go back to the 3.2 version of the plug in, it is ok. [workspace] $ "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\tf" history $/AMERICAS_/Branches/xxx-Test/Source/xxxPortals/InternalPortal -recursive -stopafter:1 -noprompt -version:D2016-06-23T17:06:21Z -format:brief -server:https://tfspro.xxx.net/tfs/TFS01 Changeset User Date Comment - - -- 1240594 xxx, Oleg 4/19/2016 Branched from $/AMERICAS_xxx [workspace] $ "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\tf" workspaces -format:brief -server:https://tfspro.xxx.net/tfs/TFS01 I have a custom
