-
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
Run pip check in CI pipelines #12508
Labels
area:CI
Airflow's tests and continious integration
area:dependencies
Issues related to dependencies problems
kind:feature
Feature Requests
Comments
turbaszek
added
kind:feature
Feature Requests
area:CI
Airflow's tests and continious integration
labels
Nov 20, 2020
We'll have to fix the conflicts first ;)
|
(That list is a lot better than it used to be) |
Yes and that's not all 🗻 |
Running on latest docker image:
|
|
turbaszek
added a commit
to turbaszek/airflow
that referenced
this issue
Nov 22, 2020
This is first step to address apache#12508
This was referenced Nov 24, 2020
turbaszek
added a commit
to PolideaInternal/airflow
that referenced
this issue
Nov 25, 2020
This is first step to address apache#12508 fixup! Run pip check when to verify production images fixup! Run pip check when to verify production images
Done: airflow/scripts/docker/install_airflow.sh Line 63 in e25eea0
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:CI
Airflow's tests and continious integration
area:dependencies
Issues related to dependencies problems
kind:feature
Feature Requests
Description
We should consider adding
pip check
command in our CI system to verify that dependencies that we use (together with constrains) are fully compatible. This should be run for biggest possible user-installation (apache-airflow[all]
).Use case / motivation
Successful
pip check
is often a business requirement for releasing new version of Airflow. It assure us that all dependencies we use to build and run Airflow are compatible and we won't face any unexpected errors.Related Issues
N/A
The text was updated successfully, but these errors were encountered: