Upgrade everything on Bazel CI! #2089
Assignees
Comments
fweikert
added a commit
to fweikert/continuous-integration
that referenced
this issue
Oct 29, 2024
- Migrate all machines from c2-standard-30 to c3d-standard-30 - Grow Linux pool from 100 to 200 - Grow Windows pool from 30 to 60 - Update image creation machine from c2-standard-8 to c3d-standard-8 Progress towards bazelbuild#2089
|
For Linux VM upgrade, we need to be careful due to bazelbuild/bazel#24081 |
fweikert
added a commit
that referenced
this issue
Oct 29, 2024
- Migrate all machines from c2-standard-30 to c3d-standard-30 - Grow Linux pool from 100 to 200 - Grow Windows pool from 30 to 60 - Upgrade image creation machine from c2-standard-8 to c3d-standard-8 Progress towards #2089
meteorcloudy
added a commit
that referenced
this issue
Nov 11, 2024
- Upgraded Windows VMs to Windows Server 2022. (Had to use `windows-2022` instead of `windows-2022-core` due to an issue of installing vc build tools) - Updated the setup script to work on the new Windows version. (Python upgraded to 3.12 from 3.9, dropped python 2) Working towards #2089
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Things we should upgrade on CI:
c2-standard-30->c3d-standard-30ubuntu-2004-lts->ubuntu-2404-ltswindows-2019-core->windows-2022-coremacOS Sonoma->macOS SequoiaNew platform support:
New Linux distribution:
The text was updated successfully, but these errors were encountered: