Repository navigation
CI: Detect if build/test is needed #299
Description
Not all PRs would require full build/test pipelines (as we currently do today). For example, if a PR only touches code in cuda.core, then
- we don't need to rebuild
cuda.bindings- The build artifacts can be reused from the latest main branch
- we don't need to re-test
cuda.bindings
We should add detection logics to inform the CI workflows so that we can save CI time (and thereby reducing the costs). The same logic can be applied to nightly tests too (#294).
Activity
leofang commentedon Dec 29, 2024
This is now tracked in #329.
leofang commentedon Jan 12, 2025
We've figured out how to fetch pre-built artifacts (#357). This is unblocked.
kkraus14 commentedon Jul 31, 2026
Reopening to track the remaining dependency-aware build and test work. #1908 added changed-path gating, but the issue also calls for reusing unaffected package artifacts so those packages do not need to be rebuilt or retested.
Proposed incremental implementation (merge in order):
Expected behavior after the stack lands:
cuda_corechange: build/test cuda-core and retest downstream cuda-python; skip cuda-bindings and cuda-pathfinder.cuda_bindingschange: build/test bindings, core, and cuda-python; skip cuda-pathfinder.cuda_pathfinderor shared-infrastructure change: run the full downstream closure.The planner/matrix does not need dedicated unit tests. We will validate the workflows with pre-commit/actionlint and then exercise package-only changes iteratively in the order cuda-core, cuda-bindings, and cuda-pathfinder.