potiuk opened a new pull request #13562:
URL: https://github.com/apache/airflow/pull/13562


   This change slightly optimizes waiting for prod images. Waiting
   for images necessarily takes one slot from jobs queue, even if
   those jobs do nothing at all. This is unfortunate, but seems
   there is no easy way to do it differently because GitHub
   Actions does not support yet cross-workflow dependencies.
   
   This PR optimizes waiting for images in the way that PROD images
   and CI images waiting happen sequentially rather than in parallell.
   
   PROD images are, as of #13557 prepared sequentially which
   means that there is no point to wait for PROD images in parallel
   to CI images.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md).
   


----------------------------------------------------------------
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]


Reply via email to