Run airflow-ctl integration tests conditionally on airflowctl changes #60010
+74
−0
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.
Following up support to: #60007
Previously, airflow-ctl integration tests would run whenever the PROD image was built, regardless of whether airflow-ctl files changed. This meant changes to Kubernetes, helm, or other unrelated files would trigger unnecessary airflow-ctl integration test runs and it would not run when only airflowctl changes were made but not K8s or helm (to trigger prod image built)
Made a change to fix that now, right now the working is such:
airflow-ctl/...airflow-ctl-tests/...chart/...kubernetes-tests/...airflow-core/src/airflow/ui/...^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.