This is an automated email from the ASF dual-hosted git repository. potiuk pushed a commit to branch v2-2-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 08dd841d50896fa17b6ac80136923f6e9e1626c3 Author: Jarek Potiuk <[email protected]> AuthorDate: Fri Jan 21 10:20:28 2022 +0100 Update md5 information about image after waiting (#21000) When "wait_for_image" was called, the information that the image was built (including the information about md5 hashes of important files) had not been stored locally. It was only stored when image was pulled by "prepare_image". Constraints job uses wait for image, because it runs in parallel for all python versions. With recent changes, the flag that image had never been built, automatically generates image build - unnecessarily, because the image is already pulled by "wait_for_image". It made almost no difference for "regular builds" because the image is rebuilt from cache (which is now very quick) but in case of PRs that change setup.py it caused image rebuild. Additionally if this iamge has conflicting requirement, it would cause build failure. The change simply registers the fact that image is "ok" so that no attempt to rebuild image happens when constraints are generated. (cherry picked from commit e5da9bf6c985593b9aa624fbb89ed052d871debf) --- scripts/ci/images/ci_wait_for_and_verify_ci_image.sh | 2 ++ 1 file changed, 2 insertions(+) diff --git a/scripts/ci/images/ci_wait_for_and_verify_ci_image.sh b/scripts/ci/images/ci_wait_for_and_verify_ci_image.sh index fb93e56..7bbd9c9 100755 --- a/scripts/ci/images/ci_wait_for_and_verify_ci_image.sh +++ b/scripts/ci/images/ci_wait_for_and_verify_ci_image.sh @@ -38,4 +38,6 @@ if [[ ${VERIFY_IMAGE=} != "false" ]]; then verify_image::verify_ci_image "${image_name_with_tag}" fi +md5sum::update_all_md5_with_group + docker_v tag "${image_name_with_tag}" "${AIRFLOW_CI_IMAGE}"
