-
Notifications
You must be signed in to change notification settings - Fork 719
Pipeline to facilitate Roslyn Copilot publish #8508
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
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@dibarbet : Is there an infra problem causing these test failures? I wouldn't expect these changes to fail the build. I could also use another review on this as well so I can close this out :) |
Yeah looks like there are some new flaky tests |
Have one question here - #8508 (comment) |
And responded : #8508 (comment) :) I'm happy to chat if you feel strongly though. |
/azp run dotnet.vscode-csharp |
Azure Pipelines successfully started running 1 pipeline(s). |
you should be able to just re-queue the individual job (either from the github checks page or AzDo page |
This pipeline ensures we get the latest roslyn copilot bits. IT needs to be approved explicitly from someone with a SAW, so I've left it as a manual trigger for now. I could imagine a release flow though that auto triggers some of these and that one person with a SAW makes all the approvals needed at once.
Pipeline is here: https://devdiv.visualstudio.com/DevDiv/_build?definitionId=27222