potiuk commented on PR #51908: URL: https://github.com/apache/airflow/pull/51908#issuecomment-2986911975
> We still need Breeze to be installed in local env containers in the CI. We can tweak the CI but we would hit the hard unique workflow limit again or end up bespoke if statements. We can call uv run now even without Breeze in the CI, which can also eliminate installing Breeze into the local env. Actually we still can use breeze - but breeze does not **really** need the CI image to run (once I make the PR green) - which has the nice feature of providing a unified simple interface to run tests (`breeze testing airflow-ctl --python version) - with auto-complete `--verbose`, `--dry-run` and other stuff. I was thinking whethere we want to remove breeze call altogether - but likely not. This serves different purpose - with `breeze` we have an easy way to replicate **exactly** what CI is doing - easily (so for example for new contributors it's super easy to run all tests). With `uv run` manually and running pytest manually - the power-users might do much more because they can run pytest directly with all the bells and whistles and without using breeze. I think I would like to stick with the pattern that all `CI` workflows are triggered with breeze, while - for the more isolated cases - allowing the developers to run as many tests as possible using direct `uv run`. WDYT @bugraoz93 and others ? -- 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]
