Much simpler way to run provider compatibility tests#39883
Merged
potiuk merged 1 commit intoapache:mainfrom May 28, 2024
Merged
Much simpler way to run provider compatibility tests#39883potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
Member
Author
|
cc: @kacpermuda -> this will be way easier to reproduce compatibilty tests (for example with open lineage) |
899563a to
113b04d
Compare
Contributor
|
Removed myself from reviewer - have taken a look to the code but I've never been with any releases (yet) and feel I have no clue how to test. I'd pass the reviewer rather to others. By the way - had the same issue with docker on the Github runner, in my case one retry helped. Do not understand why it fails with the network stuff. |
113b04d to
dcd1036
Compare
This PR adds much easier way to run provider compatibility tests locally. There is no longer need to build provider packages locally to run the tests. Simply run: ```shell breeze shell --use-airflow-version 2.x.y \ --mount-sources providers-and-tests ``` This will get the right airflow version and mount provider code and tests appropriately so that you can conveniently iterate with the tests and providers locally and run tests in breeze environment against arbitrary airflow version.
dcd1036 to
3113f08
Compare
eladkal
approved these changes
May 27, 2024
dirrao
approved these changes
May 28, 2024
fdemiane
pushed a commit
to fdemiane/airflow
that referenced
this pull request
Jun 6, 2024
This PR adds much easier way to run provider compatibility tests locally. There is no longer need to build provider packages locally to run the tests. Simply run: ```shell breeze shell --use-airflow-version 2.x.y \ --mount-sources providers-and-tests ``` This will get the right airflow version and mount provider code and tests appropriately so that you can conveniently iterate with the tests and providers locally and run tests in breeze environment against arbitrary airflow version.
romsharon98
pushed a commit
to romsharon98/airflow
that referenced
this pull request
Jul 26, 2024
This PR adds much easier way to run provider compatibility tests locally. There is no longer need to build provider packages locally to run the tests. Simply run: ```shell breeze shell --use-airflow-version 2.x.y \ --mount-sources providers-and-tests ``` This will get the right airflow version and mount provider code and tests appropriately so that you can conveniently iterate with the tests and providers locally and run tests in breeze environment against arbitrary airflow version.
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
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.
This PR adds much easier way to run provider compatibility tests locally. There is no longer need to build provider packages locally to run the tests. Simply run:
This will get the right airflow version and mount provider code and tests appropriately so that you can conveniently iterate with the tests and providers locally and run tests in breeze environment against arbitrary airflow version.
^ 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 newsfragments.