potiuk commented on pull request #13767: URL: https://github.com/apache/airflow/pull/13767#issuecomment-770428606
Hey @kaxil @ash @mik-laj - I got - I think - final version of the provider PR finally working and green. It will fail here because it needs to be merged to MASTER to succeed but I got it running and "green" in my own fork here: https://github.com/potiuk/airflow/actions/runs/525666213 The output is now sooo much nicer and shows exactly what's going on so that it is easy to grasp it. The logs are nicely folded in groups and all is colored. Also errors are much better visible, red and pop-out immediately. Some screenshots are taken from the CI job, but similar output you get as release manager when you are running ./breeze commands to see how many of the packages need version bump: Building PROD image using provider packages:  You can see that first all provider packages are built, then the main airflow package and the PROD image is built using those provider packages (by unfolding each package build you can see exact commands in each of the steps for each package: * generating setup files * checking if suffixes are fine * building the package Preparing provider documentation: You can see an example output genmerated by new neo4j proivider (fresh provider):  Similar output for packages that had some changes but their version has not been updated:  And another one when when the version is already updatead and package is ready for release:  We also build and test ALL provider packages in the CI build separately (in PROD image build we only build a subset of those :  In the "regular" provider's package. We install all the providers, see if everything can be imported and we test all `airflow providers` command to see if everything is good:  For Backport providers we just check if the backport providers can be installed in latest 1.10.* released (1.10.14 now):  ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
