[CI] Add preferCached for docker-startup commands#244766
Merged
delanni merged 3 commits intoDec 4, 2025
Merged
Conversation
delanni
added
Team:Operations
Contributor
|
Pinging @elastic/kibana-operations (Team:Operations) |
csr
approved these changes
Dec 2, 2025
botelastic
Bot
added
ci:project-deploy-observability
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
Contributor
|
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services) |
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
nchaulet
approved these changes
Dec 2, 2025
jbudz
approved these changes
Dec 2, 2025
botelastic
Bot
added
the
Team:obs-presentation
Contributor
|
Pinging @elastic/obs-presentation-team (Team:obs-presentation) |
delanni
removed
the
ci:project-deploy-observability
Member
Author
|
/ci |
Contributor
💚 Build Succeeded
Metrics [docs]Public APIs missing comments
History
|
rmyz
approved these changes
Dec 4, 2025
botelastic
Bot
added
the
ci:project-deploy-observability
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
rmyz
removed
the
Team:obs-ux-infra_services - DEPRECATED
joeypoon
approved these changes
Dec 4, 2025
tomsonpl
approved these changes
Dec 4, 2025
Contributor
|
Starting backport for target branches: 8.19, 9.1, 9.2 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 4, 2025
## Summary Add `preferCached` as an option in the test util for starting docker images, turn it on for all EPR image pulls, in order to prevent costly docker pulls in FTRs/integration tests. After elastic#244517 we still have a small temporal zone in between an agent being provisioned and the tests being ran, where a promotion would trigger a docker pull, that depletes disk space, it also would make pulls slow, and potentially time out tests. This PR suggests, we should always use the cached variant (for EPR at least). With this, the above risk zone is no longer causing pulls, it's just that we are still testing the previously promoted and cached image, probably not risky. (cherry picked from commit 5336f0d)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 4, 2025
## Summary Add `preferCached` as an option in the test util for starting docker images, turn it on for all EPR image pulls, in order to prevent costly docker pulls in FTRs/integration tests. After elastic#244517 we still have a small temporal zone in between an agent being provisioned and the tests being ran, where a promotion would trigger a docker pull, that depletes disk space, it also would make pulls slow, and potentially time out tests. This PR suggests, we should always use the cached variant (for EPR at least). With this, the above risk zone is no longer causing pulls, it's just that we are still testing the previously promoted and cached image, probably not risky. (cherry picked from commit 5336f0d)
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Dec 4, 2025
## Summary Add `preferCached` as an option in the test util for starting docker images, turn it on for all EPR image pulls, in order to prevent costly docker pulls in FTRs/integration tests. After elastic#244517 we still have a small temporal zone in between an agent being provisioned and the tests being ran, where a promotion would trigger a docker pull, that depletes disk space, it also would make pulls slow, and potentially time out tests. This PR suggests, we should always use the cached variant (for EPR at least). With this, the above risk zone is no longer causing pulls, it's just that we are still testing the previously promoted and cached image, probably not risky. (cherry picked from commit 5336f0d)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Dec 4, 2025
…245213) # Backport This will backport the following commits from `main` to `9.2`: - [[CI] Add `preferCached` for docker-startup commands (#244766)](#244766) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-12-04T09:54:11Z","message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","Team:Fleet","backport:all-open","ci:project-deploy-observability","v9.3.0","Team:obs-presentation"],"title":"[CI] Add `preferCached` for docker-startup commands","number":244766,"url":"https://github.com/elastic/kibana/pull/244766","mergeCommit":{"message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/244766","number":244766,"mergeCommit":{"message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Dec 4, 2025
…245212) # Backport This will backport the following commits from `main` to `9.1`: - [[CI] Add `preferCached` for docker-startup commands (#244766)](#244766) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-12-04T09:54:11Z","message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","Team:Fleet","backport:all-open","ci:project-deploy-observability","v9.3.0","Team:obs-presentation"],"title":"[CI] Add `preferCached` for docker-startup commands","number":244766,"url":"https://github.com/elastic/kibana/pull/244766","mergeCommit":{"message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/244766","number":244766,"mergeCommit":{"message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
kibanamachine
added a commit
that referenced
this pull request
Dec 4, 2025
…245211) # Backport This will backport the following commits from `main` to `8.19`: - [[CI] Add `preferCached` for docker-startup commands (#244766)](#244766) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-12-04T09:54:11Z","message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507","branchLabelMapping":{"^v9.3.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","Team:Fleet","backport:all-open","ci:project-deploy-observability","v9.3.0","Team:obs-presentation"],"title":"[CI] Add `preferCached` for docker-startup commands","number":244766,"url":"https://github.com/elastic/kibana/pull/244766","mergeCommit":{"message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.3.0","branchLabelMappingKey":"^v9.3.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/244766","number":244766,"mergeCommit":{"message":"[CI] Add `preferCached` for docker-startup commands (#244766)\n\n## Summary\nAdd `preferCached` as an option in the test util for starting docker\nimages, turn it on for all EPR image pulls, in order to prevent costly\ndocker pulls in FTRs/integration tests.\n\nAfter #244517 we still have a small temporal zone in between an agent\nbeing provisioned and the tests being ran, where a promotion would\ntrigger a docker pull, that depletes disk space, it also would make\npulls slow, and potentially time out tests.\n\nThis PR suggests, we should always use the cached variant (for EPR at\nleast). With this, the above risk zone is no longer causing pulls, it's\njust that we are still testing the previously promoted and cached image,\nprobably not risky.","sha":"5336f0d72e870adfed881b0720cfbeb84e261507"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co>
JordanSh
pushed a commit
to JordanSh/kibana
that referenced
this pull request
Dec 9, 2025
## Summary Add `preferCached` as an option in the test util for starting docker images, turn it on for all EPR image pulls, in order to prevent costly docker pulls in FTRs/integration tests. After elastic#244517 we still have a small temporal zone in between an agent being provisioned and the tests being ran, where a promotion would trigger a docker pull, that depletes disk space, it also would make pulls slow, and potentially time out tests. This PR suggests, we should always use the cached variant (for EPR at least). With this, the above risk zone is no longer causing pulls, it's just that we are still testing the previously promoted and cached image, probably not risky.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
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.
Summary
Add
preferCachedas an option in the test util for starting docker images, turn it on for all EPR image pulls, in order to prevent costly docker pulls in FTRs/integration tests.After #244517 we still have a small temporal zone in between an agent being provisioned and the tests being ran, where a promotion would trigger a docker pull, that depletes disk space, it also would make pulls slow, and potentially time out tests.
This PR suggests, we should always use the cached variant (for EPR at least). With this, the above risk zone is no longer causing pulls, it's just that we are still testing the previously promoted and cached image, probably not risky.
Closes: #244476