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

Error with TFS Plugin

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Hi,
      From the past few day, I have started getting error with my TFS Plugin integrated with Jenkins. I have tried clearing the tfs cache but nothing helped.

      Below is the stack trace:

      FATAL: java.lang.NullPointerException: webService must not be null
      java.lang.RuntimeException: java.lang.NullPointerException: webService must not be null
      at hudson.plugins.tfs.model.Server.execute(Server.java:226)
      at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:272)
      at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:268)
      at hudson.plugins.tfs.model.Project.getRemoteChangesetVersion(Project.java:284)
      at hudson.plugins.tfs.TeamFoundationServerScm.recordWorkspaceChangesetVersion(TeamFoundationServerScm.java:359)
      at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:308)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
      at hudson.model.Run.execute(Run.java:1720)
      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.NullPointerException: webService must not be null
      at com.microsoft.tfs.util.Check.throwForNull(Check.java:116)
      at com.microsoft.tfs.util.Check.notNull(Check.java:22)
      at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.<init>(VersionControlClient.java:439)
      at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.<init>(VersionControlClient.java:515)
      at com.microsoft.tfs.core.config.client.DefaultClientFactory$7.newClient(DefaultClientFactory.java:228)
      at com.microsoft.tfs.core.config.client.DefaultClientFactory.newClient(DefaultClientFactory.java:92)
      at com.microsoft.tfs.core.TFSConnection.getClient(TFSConnection.java:1459)
      at com.microsoft.tfs.core.TFSTeamProjectCollection.getVersionControlClient(TFSTeamProjectCollection.java:376)
      at hudson.plugins.tfs.model.Server.getVersionControlClient(Server.java:207)
      at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:56)
      at hudson.plugins.tfs.commands.RemoteChangesetVersionCommand.call(RemoteChangesetVersionCommand.java:33)
      at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
      at hudson.plugins.tfs.model.Server.execute(Server.java:222)
      ... 13 more
      Finished: FAILURE

        Attachments

          Activity

          Hide
          kimcm Kim Meiser added a comment -

          This advice solved the problem on my machine: Try to clear the Team Foundation Cache, as described here: https://blogs.msdn.microsoft.com/vsalm/2013/12/17/how-to-clear-the-tfs-cache-on-client-machines/

           

          Show
          kimcm Kim Meiser added a comment - This advice solved the problem on my machine: Try to clear the Team Foundation Cache, as described here: https://blogs.msdn.microsoft.com/vsalm/2013/12/17/how-to-clear-the-tfs-cache-on-client-machines/  
          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:
            000panther Paul Weber
            Reporter:
            sipandey Siddharth Pandey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: