jessehouwing
commented
6 years ago Quite likely related to #55.
I've asked Microsoft to look into this, as it looks like an agent thing. It would be very helpful if you could provide a few additional detail:
- [ ] Agent version
- [ ] How was the build triggered? Manual? CI? Gated? Through an API somehow?
- [ ] Do your version control mappings contain variables?
- [ ] Custom agent or Hosted agent
- [ ] Full debug logs of the initialize and get source control steps.
- [ ] Full debug logs of the Check-in changes step.
jkwinder
We've had good success with this task in one vsts instance, but after moving the build definition and repo to a different vsts instance, we cannot get this task to work there. One issue that occurs is that the Build_Repository_Name environment variable has no value and that causes an error on Get-ServiceEndpoint as near as we can tell. There really are no differences in the build agent between the two environments (they are running on the same VM) nor are there any differences in the build definition. We've looked into differences with the collection permissions for the service account which runs the build agent and can't see anything that would be causing this problem Does anyone have any idea why that variable wouldn't be set? We've also tried explicitly setting that variable, but then encounter another error shortly afterwards.