This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new 5a8d9d644d Remove --force-build command in cache steps in CI (#35784)
5a8d9d644d is described below

commit 5a8d9d644d1450486d1471f107adeec3e07bcd5d
Author: Jarek Potiuk <[email protected]>
AuthorDate: Tue Nov 21 19:40:02 2023 +0100

    Remove --force-build command in cache steps in CI (#35784)
    
    The `--force-build` command has not been used for a long time
    in the `ci-image build` command for quite some time because the
    sheer fact that you run the command means that you want to run
    the build (so it made no sense to have it). The command only makes
    sense when you want to force build when running `breeze` or
    `breeze start-airflow` command.
    
    However commands to build cache in CI still had this command used
    and it caused the builds to fail after merging #35768 when the
    option has been removed (it was not detected there, because
    cache steps only run in main build)
---
 .github/workflows/ci.yml | 2 --
 1 file changed, 2 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 45e0a9fca0..1e8eabc7a5 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -232,7 +232,6 @@ jobs:
           --builder airflow_cache
           --prepare-buildx-cache
           --run-in-parallel
-          --force-build
           --platform ${{ matrix.platform }}
         env:
           DEBUG_RESOURCES: ${{needs.build-info.outputs.debug-resources}}
@@ -1890,7 +1889,6 @@ jobs:
           --builder airflow_cache
           --prepare-buildx-cache
           --run-in-parallel
-          --force-build
           --platform ${{ matrix.platform }}
         env:
           DEBUG_RESOURCES: ${{needs.build-info.outputs.debug-resources}}

Reply via email to