This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a commit to branch v2-8-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 528d2bc51be862950ff86e815c33fdd78c71c175
Author: Jarek Potiuk <ja...@potiuk.com>
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}}
