-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REGRESSION]: npmAuthenticate silently fails authenticate to Azure Devops npm feeds #20361
Comments
Similar issue here: Breaking task version0.244.3 Last working task version0.238.3 Relevant log output
|
Same here. Also reverted to |
@embetten I see you've been working on this task, would you be able to say if this issue will be looked at soon? |
@sgtwilko The issue is being looked into, however I haven't been able to get a repro on my end (using the affected version).
|
@AlexVTor I am facing the same issue:
Is there a a way to upload the log files hidden from public view? as these contain sensitive information - happy to email over if required. |
@TRStarr Thanks for offering your help here. I don't think there's a way to upload files without them being available to others. I can think of two other approaches.
Thanks again for your assistance |
Hey @AlexVTor happy to confirm 0.246.3 is working all hunky dory! thank you very much for fixing this!! |
Thanks for the feedback! I've heard the same feedback on other fronts as well, so I will close this issue. If there are any more issues, please re-open or post here. |
New issue checklist
Task name
npmAuthenticate
Breaking task version
0.244.1
Last working task version
0.238.3
Regression Description
Although the task appears to work, when using
npm ci
packages being installed from our org scoped feed fail to install due to 401 authentication failures.When reverting to version 0.238.3 of the
npmAuthenticate
task the subsequentnpm ci
task completes successfully.Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
windows-2019
Relevant log output
Full task logs with system.debug enabled
See above:
UNSUCCESSFUL RUN
SUCCESSFUL RUN
Repro steps
The text was updated successfully, but these errors were encountered: