Run promote-images in parallel to test-images on branches other than main/release #10267
+32
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
trigger-e2e-tests
waits half an hour before starting to run. Nearly half of that time can be saved by promoting images before tests on them are complete, so the e2e tests can run in parallel.On
main
andrelease{,-proxy,-compute}
,promote-images
updateslatest
and pushes things to prod ecr, so we want to runpromote-images
only aftertest-images
is done, but on other branches, there is no harm in promoting images that aren't tested yet.Summary of changes
To promote images into dev container registries sooner,
promote-images
is split intopromote-images-dev
andpromote-images-prod
. The former pushes to dev container registries, the latter to prod ones. The latter also waits fortest-images
, while the former doesn't. This allows to runtrigger-e2e-tests
sooner.