-
Notifications
You must be signed in to change notification settings - Fork 353
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
dotnet-tools feed started to require authentication #9490
Comments
All runtime, dotnet-monitor builds are also affects Created an ICM for this https://portal.microsofticm.com/imp/v3/incidents/details/310473385/home |
We are also seeing this:
Seems like it's a similar issue |
Original IcM was closed as it was routed badly. I opened a new one for Azure DevOps: https://portal.microsofticm.com/imp/v3/incidents/details/310579759/home All builds are still failing, waiting for M1 approval to upgrade to Sev 2 |
The feature flag that caused this was reverted and we're back on track. @mmitche you might be interested in this - the feature flag was for allowing public feeds to have upstreams - so something we're probably waiting for for some time already. Seems like we're going to have to wait some more :) |
Reopening to force known issues automation to update the issue with impacted builds |
Now that we have impact data, closing issue. |
Build
Looks like this is affecting roslyn-ci builds for the past hour or so. I used the "Report infrastructure issue" button in Helix Build Analysis to fill this out. It was very handy!
https://dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_build/results?buildId=1792333
cc @333fred whose build is affected
Build leg reported
Restore
Pull Request
dotnet/roslyn#61551
Action required for the engineering services team
To triage this issue (First Responder / @dotnet/dnceng):
If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:
Additional information about the issue reported
No response
Report
Summary
The text was updated successfully, but these errors were encountered: