potiuk edited a comment on pull request #17635: URL: https://github.com/apache/airflow/pull/17635#issuecomment-900164110
> Wait -- we rebuilt the images, meaning that the images we pushed _aren't_ the ones we just ran tests against? That doesn't seem like desirable behaviour to me. It's all deliberate. We do it because the original images in push/schedule perform "eager upgrade" of constraints. If we push those images used for tests, then the cache for those images will be invalidated at the step where the eager upgrade is performed (because regular pull requests do not perform eager upgrade). The result of the eager-upgrade in previous steps is that we have a new set of constraints that get pushed automatically. And then we use those constraints to build the new images (this time without eager upgrade so that they can be used as cache for regular PR builds that do not perform "eager upgrade". This is why I recently reverse the steps. First constraints are pushed and only after that the "cache images" are rebuilt using those new constraints. -- 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]
