Allow specifying source branch for test splitting timing data
J
Jasper Lin
Currently, test splitting by timing uses the following fallback logic:
Latest job's test results from the same branch and if no data exists, falls back to latest job's test results from ANY branch in the project.
Requested Feature:
Add configuration option to specify which branch's timing data should be used for test splitting, such as:
- circleci tests split --split-by=timings --timing-branch=main
Or a configuration at the job level:
jobs:
test:
restore_test_results:
timing_source: main # Only use timing data from main branch
Why This Matters:
Bugs or performance issues in PR builds shouldn't corrupt the timing baseline for all subsequent builds
Partial test runs in branches produce incomplete timing data that leads to poor test distribution
Teams need predictable, reliable test splitting based on a stable timing baseline