Only run testable integrations relevant to the change in selective checks#68112
Open
potiuk wants to merge 1 commit into
Open
Only run testable integrations relevant to the change in selective checks#68112potiuk wants to merge 1 commit into
potiuk wants to merge 1 commit into
Conversation
…ecks Previously breeze selective checks emitted the full list of testable core and provider integrations on every run where unit tests ran, so a PR touching a single provider still spun up every integration-system-test service. Narrow the emitted integrations: - all-tests/canary runs still emit every integration - a provider integration is emitted only when its owning provider is among the affected providers of the change - the core kerberos/otel/redis integrations are emitted only when their corresponding core source group changed (new KERBEROS/OTEL/CELERY file groups; redis maps to the core executor sources, celery's backend)
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
boring-cyborg
Bot
added
area:dev-tools
backport-to-v3-2-test
shahar1
approved these changes
Jun 6, 2026
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
2 participants
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.
Previously breeze
selective-checksemitted the full list of testable coreand provider integrations on any run where unit tests run, so a PR touching a
single provider still spun up every integration-system-test service (kerberos,
otel, redis, celery, mongo, trino, ...), wasting CI capacity.
This narrows the emitted integrations:
dispatch) still emit every testable integration — no change.
provider is among the affected providers of the change (new
TESTABLE_PROVIDERS_INTEGRATION_OWNERSmapping).kerberos/otel/redisare emitted only when theircorresponding core source group changed — new
KERBEROS_FILES,OTEL_FILESand
CELERY_FILESfile groups.redismaps to the core executor sources(redis is celery's broker/result backend).
CI-disabled and ARM-disabled filtering is preserved across all branches.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines