From 39eb7d09dc35213f4aac6b86d25f18d277f9431b Mon Sep 17 00:00:00 2001 From: Alex Szabo Date: Mon, 10 Mar 2025 10:56:15 +0100 Subject: [PATCH] [ci] Trigger VM image rebuild for cache rebuild only (#213497) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## Summary When VM image rebuild is triggered after ES promotion, only the cache warmup should be built. This PR also separates the daily full build to a daily base + cache build (in case ES promotions are failing for some reason, we should still have a daily cache refresh). Requires: https://github.com/elastic/ci-agent-images/pull/1295 With this, we'd run a daily base image build and cache build (~40m + 25m) + cache warmups for every promotion (~4x 25m) instead of a full build and promotion per build (~4x 55m). Ultimately not that much of a gain 🤷 (4*55=220m => 40+5x25=165m) (cherry picked from commit 830dbd4ed72cb05829dbc1ee383dee9f9cbcdac8) # Conflicts: # .buildkite/pipeline-resource-definitions/kibana-vm-images.yml # .buildkite/scripts/steps/es_serverless/promote_es_serverless_image.sh # .buildkite/scripts/steps/fleet/promote_package_registry.sh --- .buildkite/scripts/steps/es_snapshots/promote.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.buildkite/scripts/steps/es_snapshots/promote.sh b/.buildkite/scripts/steps/es_snapshots/promote.sh index 2b85505619a95..9f249680dd851 100755 --- a/.buildkite/scripts/steps/es_snapshots/promote.sh +++ b/.buildkite/scripts/steps/es_snapshots/promote.sh @@ -25,6 +25,7 @@ steps: async: true build: env: - IMAGES_CONFIG: "kibana/images.yml" + IMAGES_CONFIG: 'kibana/image_cache.yml' + BASE_IMAGES_CONFIG: 'core/images.yml,kibana/base_image.yml' RETRY: "1" EOF