-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup.cfg change triggers full build #12684
Setup.cfg change triggers full build #12684
Conversation
Since we moved part of the setup.py specification to setup.cfg, we should trigger full build when only that file changes.
@ashb - after the dependencies were moved to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whops, thought I did this.
Clearly not
The PR needs to run all tests because it modifies core of Airflow! Please rebase it to latest master or ask committer to re-run it! |
Probably only in Breeze. This one is a selective check in CI - and those are different criteria. For Breeze change in the file triggers the need for image build. For selective checks, it triggers "all tests" |
Since we moved part of the setup.py specification to setup.cfg, we should trigger full build when only that file changes. (cherry picked from commit e4ab453)
Since we moved part of the setup.py specification to setup.cfg, we should trigger full build when only that file changes. (cherry picked from commit e4ab453)
Since we moved part of the setup.py specification to setup.cfg, we should trigger full build when only that file changes. (cherry picked from commit e4ab453)
Since we moved part of the setup.py specification to setup.cfg, we should trigger full build when only that file changes. (cherry picked from commit e4ab453)
Since we moved part of the setup.py specification to
setup.cfg, we should trigger full build when only that file
changes.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.