forked from apache/airflow
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Optimize-away PROD image build in many cases (apache#35439)
We were always building PROD image when we built CI image on CI as we had only one flag "build-images" in selective checks. This was based on an assumption that we want to still run docker compose tests with airflow when any of our sources change - just to see if it still works. While "docker-compose" tests are the only end-to-end tests it is very unlikely that unit and integration tests passing will trigger a docker compose test failure. This of course might happen, but if it happens, we will find out during our canary builds that run all the tests and building PROD image in this case is a waste of resources and time - waiting for docker-compose tests to complete when we really do not have to do it makes no sense either. Even if those tests are relatively quick, just waiting for PROD images being built (PROD images have to wait for CI images in order to get constraints from CI builds) adds quite a bit of elapsed test time for many smaller PRs that do not change k8s or Helm in any way. This change splits "image-build" into two outputs of selective checks: ci-image-build and prod-image-build. The CI-image build is the same as before - we will build CI image whenever any test need to use the image and run our code (so for example it is false when only README files change). PROD image build is set to true now only when we need kubernetes tests (i.e. when k8s provider changes) or when chart changes - because there we want to test basic functionality of k8s integration and Helm deployment/running.
- Loading branch information
Showing
5 changed files
with
92 additions
and
52 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.