Repository navigation
ci: Vary one dimension at a time from a single origin - #132
Merged
Merged
Conversation
Mizux
reviewed
Nov 9, 2026
Collaborator
There was a problem hiding this comment.
please keep it to test XCode and Apple Clang
copybara-service
Bot
force-pushed
the
test_1017121896
branch
3 times, most recently
from
November 9, 2026 14:03
8e09340 to
cc84a6c
Compare
Each build workflow previously defined its own matrix, repeating compiler, C++ standard, build-mode, and Python-version combinations across operating systems and build systems. Even without the Intel macOS workflows, the two remaining macOS workflows spawn 6 jobs per run against GitHub Actions' 5-concurrent-macOS-job limit, and the macOS and Windows Bazel workflows build with `-c opt`, compiling most files twice (PIC and non-PIC). Restructure the 6 build workflows around a single origin (`ubuntu-26.04`, `clang-22`, Bazel `9.x`, `fastbuild`, C++17, Python 3.12) in `amd64_linux_bazel` and vary one dimension at a time from it, using a flat `matrix: include:` list across all workflows: * Compiler, C++ standard, Python version, and Bazel version variations run only on Linux, where runners are fast and plentiful, and CMake on Linux varies only CMake-specific settings (version, generator, build type). * macOS drops from 6 jobs to 2 (1 `fastbuild` job in `arm64_macos_bazel` and 1 `Xcode` multi-config job in `arm64_macos_cmake`, exercising the `APPLE` target properties and Xcode generator), and Windows Bazel switches from `opt` to `fastbuild` (retaining `windows-2022` and `-c dbg` for MSVC `_DEBUG`). * `arm64_macos_cmake` and `amd64_windows_cmake` are kept as single jobs even though their OSes and CMake are already tested separately, because our CMake config has `APPLE`, `WIN32` (`BUILD_SHARED_LIBS=ON` DLL copy), and multi-config (`Xcode` / Visual Studio `LIBRARY_OUTPUT_DIRECTORY`) logic that Linux CMake and Bazel do not exercise. PiperOrigin-RevId: 1017290821
copybara-service
Bot
force-pushed
the
test_1017121896
branch
from
November 9, 2026 14:16
cc84a6c to
c243b16
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ci: Vary one dimension at a time from a single origin
Each build workflow previously defined its own matrix, repeating compiler,
C++ standard, build-mode, and Python-version combinations across operating
systems and build systems. Even without the Intel macOS workflows, the two
remaining macOS workflows spawn 6 jobs per run against GitHub Actions'
5-concurrent-macOS-job limit, and the macOS and Windows Bazel workflows
build with
-c opt, compiling most files twice (PIC and non-PIC).Restructure the 6 build workflows around a single origin (
ubuntu-26.04,clang-22, Bazel9.x,fastbuild, C++17, Python 3.12) inamd64_linux_bazeland vary one dimension at a time from it, using a flatmatrix: include:list across all workflows:only on Linux, where runners are fast and plentiful, and CMake on Linux
varies only CMake-specific settings (version, generator, build type).
fastbuildjob inarm64_macos_bazeland 1
Xcodemulti-config job inarm64_macos_cmake, exercising theAPPLEtarget properties and Xcode generator), and Windows Bazelswitches from
opttofastbuild(retainingwindows-2022and-c dbgfor MSVC
_DEBUG).arm64_macos_cmakeandamd64_windows_cmakeare kept as single jobseven though their OSes and CMake are already tested separately, because
our CMake config has
APPLE,WIN32(BUILD_SHARED_LIBS=ONDLL copy),and multi-config (
Xcode/ Visual StudioLIBRARY_OUTPUT_DIRECTORY)logic that Linux CMake and Bazel do not exercise.