Nuget source credentials management #1382
Comments
exitcode is always set when an exception is hit. what is the reported error message? |
Here is the output:
|
regarding bootstrapper: if the paket.exe is already there we don't change exit code, because usually it's no issue to just proceed. |
th other one is strange. can I reproduce? |
Thanks for the explanation. If I delete paket.exe, then the bootstrapper returns as expected an errorlevel equal to 1 For the paket.exe, I think you can reproduce by using my batchfile code within a simple folder with 1 project. What matters is that either the credentials you put in the config are wrong, or the source does not exist, with a typo in the URL per example. |
I think I need your paket.dependencies and paket.lock. Sforkmann @ Gmail |
Sent! |
I'm wondering if it's worth looking at using Paket programmatically through the NuGet package in an F# script - might you be able to better reason about errors etc. rather than through a batch file? |
That's what I thought too. |
credentials are now throwing properly. |
Thanks Steffen, indeed now paket.exe returns 1 when credentials are outdated! |
How does one delete stored credentials? I was trying to troubleshoot an issue where paket cannot connect to one of our package feeds and it is now stuck failing (every time) with Edit: |
Hello,
We are preparing the introduction of Paket for managing package references in our company for our main product codebase.
The packages for this codebase are stored in an Artifactory repository with no anonymous access.
Developers need to use their LDAP company credentials to access it, the build agents are using a build account.
A developer's password changes every 3 months, the build account password never changes.
We would like to use the command paket.exe config add-credentials to solve this problem.
It works fine to restore packages once the credentials are stored.
But when using this solution, we also need to catch up the moment where the stored credentials need to change properly.
We handle calling paket.bootstrapper.exe and paket.exe from a bootstrap.bat file in the root of our codebase. I wanted to programmatically detect when paket was failing to restore packages because of credentials.
Unfortunately, neither paket.bootstrapper.exe or paket.exe are returning a proper exit code different than 0 when there is a critical error:
The simple batch script I wrote to test that, meant to be executed from the root folder of the codebase:
The text was updated successfully, but these errors were encountered: