Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-36202

Listing tfs workspaces fails with 4.1.0

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Component/s: tfs-plugin
    • Environment:
      Windows Server 2012, Jenkins 2.10, tfs-plugin 4.1.0, TFS Server 2015 update 2
    • Similar Issues:

      Description

      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.xxxxx.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_xxxx/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 workspace setup through Jenkins.

      Is there something different about how the 4.1.0 plug calls for the workspaces/history?

      I would also get the same error from the command line when running the tf command from CLC, but it works ok when ruunning the one from Visual Studio like so (string of asterisks removed after ":brief"):

      "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\tf" history $/AMERICAS_xxx/Branches/xxx-Test/Source/xxxPortals/InternalPortal -recursive -stopafter:1 -noprompt -version:D2016-06-23T15:32:09Z -format:brief -server:https://tfspro.xxx.net/tfs/TFS01

      dos that java CLC version of tf hold on to something in cache/memory/config that it shouldn't?

        Attachments

          Activity

          Hide
          legoleg Oleg N added a comment -

          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?

          Show
          legoleg Oleg N added a comment - 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?
          Hide
          legoleg Oleg N added a comment -

          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?

          Show
          legoleg Oleg N added a comment - 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?
          Hide
          kelliejos Kellie Jos added a comment -

          Thank you for using the tfs-plugin. It appears that your issue was found in an older version of the plugin. There have been a number of improvements made in the recent releases that may have resolved your issue. Please update to the most recent 5.126.0 release. If your issue persists, please open a new ticket and we will investigate.

          Show
          kelliejos Kellie Jos added a comment - Thank you for using the tfs-plugin. It appears that your issue was found in an older version of the plugin. There have been a number of improvements made in the recent releases that may have resolved your issue. Please update to the most recent 5.126.0 release. If your issue persists, please open a new ticket and we will investigate.

            People

            • Assignee:
              redsolo redsolo
              Reporter:
              legoleg Oleg N
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: