[CI] Optimize CI workflow job selection across repositories #8708

Activity

1. ScottTodd

   added

   CICDRelated to CI/CD InfraRelated to CI/CD Infra

   ci-improvementImprovements to CI infra: targeted builds, artifact reuse, workflow optimization, etc.Improvements to CI infra: targeted builds, artifact reuse, workflow optimization, etc.

   on Oct 2, 2026
2. ScottTodd

   added sub-issues on Oct 2, 2026

   • CI: scope external-repository workflow changes to their own test jobs #8514
   • [CI] Add lever system for test machines #8688
   • [CI] Teach the CI system to automatically skip build/test jobs for diffs only modifying code comments #8691
3. ScottTodd

   added 2 related issues on Oct 2, 2026

   • [ci] Add path-based skip filters for external repo builds #7777
   • [CI] Add package reuse mode that jumps straight to PyTorch/JAX builds/tests #7346
4. ScottTodd

   added sub-issues on Oct 2, 2026

   • [CI] Support Linux-only and Windows-only runs based on files modified #6943
   • [CI] Support running CPU-only tests even when GPU testing is skipped #8500
5. ScottTodd

   added a related issue on Oct 2, 2026

   • [ci] expanding and enhancing multi arch CI label #7375
6. ScottTodd

   pinned this issue on Oct 2, 2026
7. ScottTodd

   added a sub-issue on Oct 2, 2026

   • [ci] Investigate batching GPU test jobs on runners to amortize overhead #7272
8. ScottTodd commented on Oct 5, 2026

   

   ScottTodd

   on Oct 5, 2026

   MemberAuthor

   More actions

   Looking across the subissues here, I think we can scale implementation and testing of changes to this part of the CI system more effectively through some changes to the code architecture and testing strategy. Take ROCm/rocm-libraries#11439 (comment) for example, where 10+ pull requests were created just to test that commits like ROCm/rocm-libraries@7a05c67 triggered the expected jobs.

   We could add test cases using git patch files like https://github.com/ROCm/rocm-libraries/pull/11468.patch (or https://github.com/ROCm/rocm-libraries/commit/7a05c6743884c0b049ec73e620ab9bd675245125.patch) for that PR/commit from @jayhawk-commits :

   From 7a05c6743884c0b049ec73e620ab9bd675245125 Mon Sep 17 00:00:00 2001
   From: Joseph Macaranas <joseph.macaranas@amd.com>
   Date: Sat, 29 Aug 2026 00:23:05 -0400
   Subject: [PATCH] test(ci): validate rocRoller multi-arch detection
   
   ---
    shared/rocroller/CMakeLists.txt | 1 +
    1 file changed, 1 insertion(+)
   
   diff --git a/shared/rocroller/CMakeLists.txt b/shared/rocroller/CMakeLists.txt
   index 1271821962b2..d87d08649396 100644
   --- a/shared/rocroller/CMakeLists.txt
   +++ b/shared/rocroller/CMakeLists.txt
   @@ -1,6 +1,7 @@
    # Copyright Advanced Micro Devices, Inc., or its affiliates.
    # SPDX-License-Identifier:  MIT
    
   +# Temporary no-op change to validate TheRock multi-arch CI project detection.
    cmake_minimum_required(VERSION 3.25.2)
    set(ROCROLLER_VERSION 1.0.0)
    set(ROCROLLER_SOVERSION 1)

   (aside: #8691 should be able to detect that commit as a no-op and skip CI for it)

   What I'm imagining is

   • Add a directory full of testdata patch files and then some test harness code in python or with supplemental data files that checks "for this commit patch, which build/test jobs would be triggered for the pull_request event?"
   • CLI scripts that can be pointed at commits or pull requests to ask "what would the current CI code decide to do for this?"
   • CLI scripts or agent skills that can turn commits or pull requests into test cases (especially as regression tests)
   • The existing path filtering code (https://github.com/ROCm/TheRock/blob/main/build_tools/github_actions/configure_ci_path_filters.py) would have adapters to patch files as one way to get a list of modified files
   • Requesting the patch file for a PR via the API should be fast and hopefully avoids needing to git fetch commit ranges (as we've started doing more, cc @erman-gurses and @geomin12 )
   • "configure external repo ci" can still be folded into "configure ci" (as mentioned elsewhere) to make this apply evenly across PRs to TheRock and component submodules
9. geomin12

   added a sub-issue on Oct 9, 2026

   • [ci] Add path-based skip filters for external repo builds #7777