-
Notifications
You must be signed in to change notification settings - Fork 100
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
[Rollout] Production rollout 2022-11-09 #736
[Rollout] Production rollout 2022-11-09 #736
Conversation
…n-to-main [automated] Merge branch 'production' => 'main'
…ride-all Add registry override to the -all pipeline.
For the production branch, we want to build everything, both on CI and PR. This change modifies the pipelines to run the "all" pipeline for production instead of the split out pipelines.
/azp run dotnet-buildtools-prereqs-docker-all |
No pipelines are associated with this pull request. |
I think I tracked down why this isn't triggering. This page says that the webhook is missing: https://dev.azure.com/dnceng-public/public/_apps/hub/ms.vss-ciworkflow.build-ci-hub?_a=edit-build-definition&id=232&view=Tab_Triggers. @michellemcdaniel, do you or anyone on your team know how to solve that one? |
I don't see something saying a webhook is missing. Can you send me a screenshot of what you're seeing? |
/azp run dotnet-buildtools-prereqs-docker-all |
Azure Pipelines successfully started running 1 pipeline(s). |
I hadn't enabled build from forks. Fixed that, running now |
it just.... skipped everything. Crap. |
/azp run dotnet-buildtools-prereqs-docker-all |
Azure Pipelines successfully started running 1 pipeline(s). |
Ok, was missing some variables on the pipeline that I didn't realize where defined in the UI on the others. That is also fixed. |
I tracked down the blocking issues, and they are all related to the powershell 7.3.0 release, which looks to have a packaging error. See PowerShell/PowerShell#18495. We can't rollout without this issue resolved. |
abandoning this. |
No description provided.