Azure DevOps Base Urls
sitwalkstand opened this issue · 4 comments
With the change to Azure DevOps Services, the feed Urls are now different. I am currently getting the following error:
2018-11-13T18:36:03.8197559Z ##[section]Starting: Promote package to Release View
2018-11-13T18:36:03.8201380Z ==============================================================================
2018-11-13T18:36:03.8201433Z Task : Promote package to Release View
2018-11-13T18:36:03.8201473Z Description : Promotes a package to a Release View in VSTS Package Management
2018-11-13T18:36:03.8201504Z Version : 1.2.3
2018-11-13T18:36:03.8201535Z Author : Rene van Osnabrugge
2018-11-13T18:36:03.8201567Z Help : Version: 1.2.3. More Information
2018-11-13T18:36:03.8201611Z ==============================================================================
2018-11-13T18:36:07.5160095Z ##[error]The remote name could not be resolved: 'https'
2018-11-13T18:36:07.5420343Z ##[section]Finishing: Promote package to Release View
I attempted to test the current base Urls in the .ps1 file in the repo, but I get a 404. I tested this base url: https://{organization}.pkgs.visualstudio.com/DefaultCollection/_apis/packaging/feeds
Looking at the updated docs (https://docs.microsoft.com/en-us/rest/api/vsts/?view=vsts-rest-4.1) it appears that these should use this Url format:
https://feeds.dev.azure.com/{organization}/_apis/packaging/feeds/
I try to make some time for this next week
I forked the repo and got it working locally for NuGet. I wasn't sure about npm, since we don't use that for our private artifacts yet. I ended up using this REST API method for the package promotion: https://github.com/MicrosoftDocs/vsts-docs/issues/2333#issuecomment-439132832
I can submit a PR with the changes I made, if you'd like.
that would be awesome
Fixed in 1.2.10