[Security Solution Cypress] Configure cypress es_archiver tasks to allow usage of platform archives#230008
Merged
rylnd merged 2 commits intoelastic:mainfrom Jul 31, 2025
Merged
Conversation
Work done as part of elastic/kibana-team#1503 moved archives to different locations, and consequently our usage of the "platform" archives within cypress stopped working. While the solution in FTR tests is currently to fully-qualify the path to the archive, I'm continuing with the "categorized" approach we've taken with cypress, where the `type` argument denotes the base directory in which to search. A more robust solution might search in all of these places, in order, if the path is ambiguous, but for now this will fix the immediate problem. Closes elastic#229861, closes elastic#229860.
Similar to previous commit. Also adds a previously-missing unload step. Closes elastic#229859.
rylnd
force-pushed
the
rylnd/platform_archives_in_cypress
branch
from
23d221a to
2267af1
Compare
rylnd
added
Team:Detection Engine
rylnd
added
backport:version
Contributor
|
Pinging @elastic/security-detection-engine (Team:Detection Engine) |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8936[✅] Security Solution Detection Engine - Cypress: 10/10 tests passed. |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]
cc @rylnd |
PhilippeOberti
approved these changes
Jul 31, 2025
Contributor
|
Starting backport for target branches: 8.19, 9.1 https://github.com/elastic/kibana/actions/runs/16652754299 |
Contributor
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
rylnd
added a commit
to rylnd/kibana
that referenced
this pull request
Aug 1, 2025
…low usage of platform archives (elastic#230008) ## Summary Work done as part of elastic/kibana-team#1503 moved archives to different locations, and consequently our usage of the "platform" archives within cypress stopped working. While the solution in FTR tests is currently to fully-qualify the path to the archive, I'm continuing with the "categorized" approach we've taken with cypress, where the `type` argument denotes the base directory in which to search. A more robust solution might search in all of these places, in order, if the path is ambiguous, but for now this will fix the immediate problem. Addresses the following `failed-test` issues: * Closes elastic#229859 * Closes elastic#229861 * Closes elastic#229860 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed * These are not flaky tests, but consistent failures. Regardless, I triggered a 10x build just in case: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8936 - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. (cherry picked from commit cba15ef)
rylnd
added a commit
that referenced
this pull request
Aug 1, 2025
… to allow usage of platform archives (#230008) (#230284) # Backport This will backport the following commits from `main` to `9.1`: - [[Security Solution Cypress] Configure cypress es_archiver tasks to allow usage of platform archives (#230008)](#230008) * Closes #229859 * Closes #229861 * Closes #229860 <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-07-31T15:06:33Z","message":"[Security Solution Cypress] Configure cypress es_archiver tasks to allow usage of platform archives (#230008)\n\n## Summary\n\nWork done as part of https://github.com/elastic/kibana-team/issues/1503\nmoved archives to different locations, and consequently our usage of the\n\"platform\" archives within cypress stopped working.\n\nWhile the solution in FTR tests is currently to fully-qualify the path\nto the archive, I'm continuing with the \"categorized\" approach we've\ntaken with cypress, where the `type` argument denotes the base directory\nin which to search.\n\nA more robust solution might search in all of these places, in order, if\nthe path is ambiguous, but for now this will fix the immediate problem.\n\nAddresses the following `failed-test` issues:\n\n* Closes #229859\n* Closes #229861\n* Closes #229860\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n* These are not flaky tests, but consistent failures. Regardless, I\ntriggered a 10x build just in case:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8936\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"cba15ef5bd482603e1a2b668c344cde63e7d7b3d","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detection Engine","backport:version","v9.2.0","v9.1.1","v8.19.1"],"title":"[Security Solution Cypress] Configure cypress es_archiver tasks to allow usage of platform archives","number":230008,"url":"https://github.com/elastic/kibana/pull/230008","mergeCommit":{"message":"[Security Solution Cypress] Configure cypress es_archiver tasks to allow usage of platform archives (#230008)\n\n## Summary\n\nWork done as part of https://github.com/elastic/kibana-team/issues/1503\nmoved archives to different locations, and consequently our usage of the\n\"platform\" archives within cypress stopped working.\n\nWhile the solution in FTR tests is currently to fully-qualify the path\nto the archive, I'm continuing with the \"categorized\" approach we've\ntaken with cypress, where the `type` argument denotes the base directory\nin which to search.\n\nA more robust solution might search in all of these places, in order, if\nthe path is ambiguous, but for now this will fix the immediate problem.\n\nAddresses the following `failed-test` issues:\n\n* Closes #229859\n* Closes #229861\n* Closes #229860\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n* These are not flaky tests, but consistent failures. Regardless, I\ntriggered a 10x build just in case:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8936\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"cba15ef5bd482603e1a2b668c344cde63e7d7b3d"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/230008","number":230008,"mergeCommit":{"message":"[Security Solution Cypress] Configure cypress es_archiver tasks to allow usage of platform archives (#230008)\n\n## Summary\n\nWork done as part of https://github.com/elastic/kibana-team/issues/1503\nmoved archives to different locations, and consequently our usage of the\n\"platform\" archives within cypress stopped working.\n\nWhile the solution in FTR tests is currently to fully-qualify the path\nto the archive, I'm continuing with the \"categorized\" approach we've\ntaken with cypress, where the `type` argument denotes the base directory\nin which to search.\n\nA more robust solution might search in all of these places, in order, if\nthe path is ambiguous, but for now this will fix the immediate problem.\n\nAddresses the following `failed-test` issues:\n\n* Closes #229859\n* Closes #229861\n* Closes #229860\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n* These are not flaky tests, but consistent failures. Regardless, I\ntriggered a 10x build just in case:\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8936\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n- [ ] Review the [backport\nguidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)\nand apply applicable `backport:*` labels.","sha":"cba15ef5bd482603e1a2b668c344cde63e7d7b3d"}},{"branch":"9.1","label":"v9.1.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Aug 5, 2025
…low usage of platform archives (elastic#230008) ## Summary Work done as part of elastic/kibana-team#1503 moved archives to different locations, and consequently our usage of the "platform" archives within cypress stopped working. While the solution in FTR tests is currently to fully-qualify the path to the archive, I'm continuing with the "categorized" approach we've taken with cypress, where the `type` argument denotes the base directory in which to search. A more robust solution might search in all of these places, in order, if the path is ambiguous, but for now this will fix the immediate problem. Addresses the following `failed-test` issues: * Closes elastic#229859 * Closes elastic#229861 * Closes elastic#229860 ### Checklist - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed * These are not flaky tests, but consistent failures. Regardless, I triggered a 10x build just in case: https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8936 - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
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
6 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
Work done as part of https://github.com/elastic/kibana-team/issues/1503 moved archives to different locations, and consequently our usage of the "platform" archives within cypress stopped working.
While the solution in FTR tests is currently to fully-qualify the path to the archive, I'm continuing with the "categorized" approach we've taken with cypress, where the
typeargument denotes the base directory in which to search.A more robust solution might search in all of these places, in order, if the path is ambiguous, but for now this will fix the immediate problem.
Addresses the following
failed-testissues:Checklist
release_note:*label is applied per the guidelinesbackport:*labels.