-
Bug
-
Resolution: Not A Defect
-
Major
-
Windows Server 2008 R2, TFS2015
I'm trying to add a new project to Jenkins after upgrading the TFS plugin from 3.2 to 5.0 - actually it's 5.1.
Some projects work, but one specifically doesn't.
I'm getting the following error:
Started by user TC
Building in workspace E:\Jenkins\jobs[jobName]\workspace
Querying for remote changeset at '$/[tfspath]/WIP/WebService' as of 'D2016-08-31T12:59:01Z'...
Query returned no result!
FATAL: null
java.lang.NullPointerException
at hudson.plugins.tfs.model.Project.extractChangesetNumber(Project.java:273)
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:1276)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Sending e-mails to: joseph.hoppe@example.com
Finished: FAILURE
I've tried adding DefaultCollection to the TFS URL.
The polling log reports:
Started on Aug 31, 2016 8:04:00 AM
Done. Took 5.4 sec
No changes
I looked at JENKINS-33280, and manually put together the URL as the issue suggests. The URL to the TFS server works, so it seems like the job's TFS settings are correct.
Please let me know if I can provide any more information.
Update: Working with someone from Microsoft, it seems like we did not have the correct TFS permissions in place.
The command below proved that the account did not have the correct permissions:
tf print -collection:http://domain:8080/tfs/DefaultCollection -login:username $/tfspath/to/solution.sln
However, we weren't able to get the right TFS permissions in place before the project concluded.