potiuk opened a new pull request, #75621: URL: https://github.com/apache/airflow/pull/75621
The `chart/` and `airflow-ctl/` release branches only ever get backports of the Helm chart or of airflow-ctl, yet their CI selected tests from the changed files like `main` does: a backport that touched shared files ran the whole core and provider matrix. - On `chart/vX-Yx-test|stable`, Helm and Kubernetes tests always run (kustomize overlays as usual) with the CI and PROD images they need. On `airflow-ctl/vX-Y-test|stable`, the airflow-ctl tests and its integration tests run with both images. All other test jobs are off, including the PROD image's own tests and the standalone/shared-distribution tests, which get new `run-generic-prod-image-tests` and `run-generic-basic-tests` outputs. Static checks, the component's docs and the tooling tests still run. - The target branch comes from the GitHub context and must match those release-branch names; a feature branch named `chart/...` or a push in a fork is not a component branch. - Outputs are scoped with one decorator, and a test fails when a new `run_*` output is neither scoped nor listed as a general check, so a job added on `main` does not start running on those branches unnoticed. - `04_selective_checks.md` documents the rule. To take effect on `chart/v1-2x-test` and `airflow-ctl/v0-1-test`, those branches need `main`'s CI, which will follow in backports. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Opus 5 Generated-by: Claude Opus 5 following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
