GitHub user potiuk added a comment to the discussion: CI: make environment materialization scale with unique environments, not matrix jobs
As discussed in Slack. Practically all ideas here are some variants of something that is already implemented or was tested, or has been used in the past... - > our CI is a continuously living thing and many of those ideas have been tried and many of those are documented in breeze's ADRs. For example using artifacts instead of registry is because a) build job does not need write permission (which allowed us to get rid of pull_request_target workflow) b) it's actually faster, becuase the artifact API is **super** fast in Github Runners - and it effectively pulls the image and only rebuilds latest layers.. Or - we already use bare mypy-in-uv for some mypy tests that do not require providers. And we also plan to do it for core tests - once we get rid some of the last provider's dependencies. This is even documented in https://github.com/apache/airflow/issues/42632#issuecomment-2449671014 So if there are any ideas that might improve certain jobs - go for it. No need for ideation. Ideas are plenty and most already tried :) Execution is all that matters. GitHub link: https://github.com/apache/airflow/discussions/73856#discussioncomment-18647021 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
