0

In our bower.json we have this dependency:

"ourpackage": "git+https://xxx.visualstudio.com/DefaultCollection/_git/ourpackage#1.2.3"

I'm using alternate credentials and this works fine on my machine.

When I run this on Visual Studio Team Services it fails as it doesn't have my credentials. I don't want to add my personal alternate credentials to the bower.json file. Another solution would be to just add the files to our project without using bower.

Is there another solution to this?

Peter Hedberg
  • 3,487
  • 2
  • 28
  • 36

2 Answers2

2

I ran across this same issue and fixed it like this:

  1. Make sure to select Options > Allow Scripts to Access OAuth Token in the build definition.

  2. Add a powershell script task to your build definition task, before your bower install command task

    $file = "path\to\bower.json"

(Get-Content $file| ForEach-Object { $_ -replace "https://your.visualstudio.com", "https://un:$env:SYSTEM_ACCESSTOKEN@your.visualstudio.com" }) | Set-Content $file

The one caveat I found is that if you have a dependency tree of bower packages hosted on VSTS, you'll have to add all of the dependencies in the tree to your root bower.json file, i.e. package1 includes package2 in its bower.json - you'll need to include both package1 and package2 in your build project's bower.json.

Nick Spiers
  • 2,344
  • 2
  • 19
  • 31
0

Try using build access oauth token: enter image description here

Check this link for reference: Use the OAuth token to access the REST API

Eddie Chen - MSFT
  • 29,708
  • 2
  • 46
  • 60
  • How can I use that to change the bower/git credentials? – Peter Hedberg Apr 06 '16 at 09:07
  • @PeterHedberg Add a powershell step to acquire the current access token and write it into bower.josn file before build. – Eddie Chen - MSFT Apr 07 '16 at 07:44
  • Ahh, ok. I'll try that! – Peter Hedberg Apr 07 '16 at 08:10
  • I've found I need to "clean" on the "Get Sources" step. It appears that Git will maintain some remotes without the "un:" prefix, even though the file is successfully updated. You'll get an error on some packages at random: ECMDERR Failed to execute "git ls-remote --tags --heads https://xxxx.visualstudio.com/DefaultCollection/DevOps/_git/xxxxxx", exit code of #128 fatal: could not read Username for 'https://xxxx.visualstudio.com': terminal prompts disabled'. Clearing out the build directories seem to prevent this behavior. – Matthew Aug 15 '17 at 16:42