-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Backport all CI matrix changes from 7.0 to reelase/6.0 #62538
Conversation
* Drop OSX 10.13 from CI matrix * Drop OSX 10.14 from PR CI matrix
* Remove ubuntu 16.04 * Remove another occurence
* CI matrix change: debian+centos+sles * Adjust the CI matrix based on latest comments
* Rev Alpine WithNode from 3.9 to 3.13 Also, * update helix queues from 3.12 to 3.13 * add 3.14 helix queues * update performance job to install cargo from main branch * Add Alpine 3.13 in rolling CI * Add missing closing paren
* Add Windows.Server.Core.20H2 to CI matrix * add windows server 20H2 * Remove 20H2 from PR * Remove 20H2 from PR run
Tagging subscribers to this area: @directhex Issue DetailsMost of the changes are tracked there: #57947 (comment)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can't review detail of YAML changes, but I approve the change.
No tactics approval needed. |
eng/pipelines/runtime-community.yml
Outdated
@@ -0,0 +1,59 @@ | |||
trigger: none |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This template doesn't make sense to port it as it doesn't even have triggers for release/* branches.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than one comment, looks good.
This reverts commit 4199aa1.
Passing tests: https://dev.azure.com/dnceng/public/_build/results?buildId=1510275&view=results There is one unrelated failure. cc @safern |
Most of the changes are tracked there: #57947 (comment)
There is no product change so impact of the change is only in CI not in product itself.