Nuget restore for AzureDevOps failed to authenticate on CI machine
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
AzureDevOps nuget feeds aren't authenticated during CI build on our on premise build machines. Nuget alone however works with the credential providers and the env var: VSS_NUGET_EXTERNAL_FEED_ENDPOINTS
Expected behavior
Paket should be able to authenticate with AzureDevOps nuget feeds and restore packages.
Actual behavior
Paket fails to authenticate and restore nuget packages from AzureDevOps nuget feeds.
Known workarounds
Login on the buildmachine and do a manual paket restore, and wait for the UI authentication to pop up and login.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing Paket restore against an AzureDevOps NuGet feed on an on-premise CI machine, then trace how credential providers and VSS_NUGET_EXTERNAL_FEED_ENDPOINTS are handled; done means authentication and package restoration work without interactive UI login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, fsharp
- Domain
- build-system, ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100