[ci] Bump 9.5.0: route serverless Cypress to serverless ES (fix for #263740)#264100
Draft
patrykkopycinski wants to merge 23 commits intoelastic:mainfrom
Draft
[ci] Bump 9.5.0: route serverless Cypress to serverless ES (fix for #263740)#264100patrykkopycinski wants to merge 23 commits intoelastic:mainfrom
patrykkopycinski wants to merge 23 commits intoelastic:mainfrom
Conversation
…ES_FROM=snapshot
The 9.5.0 ES Docker image isn't published yet (circular dep with the
unified release), so Cypress must fall back to the snapshot tar.gz.
Re-adds `CYPRESS_ES_FROM=snapshot` in setup_job_env.sh and restores the
dynamic `${pkg.version}-SNAPSHOT` DOCKER_TAG (reverting 30d27f8). That
alone breaks *serverless* Cypress suites because parallel.ts let the env
var unconditionally override `esTestCluster.from: serverless`, so ES
booted from a stateful snapshot with serverless-only settings and
crashed with:
unknown setting [xpack.security.authc.native_roles.enabled]
unknown setting [serverless.search.enable_replicas_for_instant_failover]
Flip the precedence so a serverless config always wins, and
CYPRESS_ES_FROM only influences stateful runs.
Contributor
Author
|
/ci |
Contributor
|
🤖 Jobs for this PR can be triggered through checkboxes. 🚧
ℹ️ To trigger the CI, please tick the checkbox below 👇
|
Contributor
Author
|
/ci |
Contributor
Author
Build 429856 — fix validated, 2 unrelated flakes blocking greenFix-validated signals (all green on this build):
Failures (2, both unrelated to this PR):
Retrying via |
Contributor
Author
|
/ci |
5 tasks
Contributor
Author
Build 430018 — core fix validated, 2 tracked-flake failuresAll failures on this build are pre-existing, tracked Scout flakes unrelated to this PR's diff (
The ES provisioning fix itself is validated — every Security Solution Cypress job on this build has passed. Retrying to let the flakes pass on retry. /ci |
Contributor
Author
|
/ci |
1 similar comment
Contributor
Author
|
/ci |
Contributor
Author
|
/ci |
2 similar comments
Contributor
Author
|
/ci |
Contributor
Author
|
/ci |
Contributor
Author
|
/ci |
1 similar comment
Contributor
Author
|
/ci |
Contributor
Author
Build 430124 — ✅ fully greenAll 408 jobs passed on the merged-with-main HEAD ( Follow-up / long-term solution: #264218 auto-detects when the matching ES Docker image isn't yet published (so the same scenario doesn't block future 9.6.0 / 9.7.0 / ... bumps). Already green on its own CI. |
Contributor
💚 Build Succeeded
Metrics [docs]
History
|
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
Parallel draft of #263740 with the CI fix applied so I can babysit the build while the main PR stays in place.
The 9.5.0 ES Docker image isn't published yet (circular dep with the unified release), so Cypress must fall back to the snapshot tar.gz. This PR:
DOCKER_TAG = \${pkg.version}-SNAPSHOT`and re-addsexport CYPRESS_ES_FROM=snapshotinsetup_job_env.sh. Without this, stateful Cypress pulled ES 9.4.0 against Kibana 9.5.0 and crashed withThis version of Kibana (v9.5.0-SNAPSHOT) is incompatible with the following Elasticsearch nodes in your cluster: v9.4.0`.CYPRESS_ES_FROMscope inx-pack/solutions/security/plugins/security_solution/scripts/run_cypress/parallel.tsso it only overrides the stateful path. Without this, 58d9e42's earlier snapshot attempt broke serverless Cypress suites because a stateful tar.gz rejectedxpack.security.authc.native_roles.enabledandserverless.search.enable_replicas_for_instant_failoverasunknown setting.Net effect: stateful Cypress uses the snapshot tar.gz, serverless Cypress keeps using
kibana-ci/elasticsearch-serverless, and the Kibana/ES version match is restored.Diff (3 files, +14/−3)
.buildkite/scripts/common/setup_job_env.shsrc/platform/packages/shared/kbn-es/src/utils/docker.tsx-pack/solutions/security/plugins/security_solution/scripts/run_cypress/parallel.tsTest plan
/ci— wait for green build on stateful + serverless Cypress jobs (Defend Workflows, Security Solution, Osquery, etc.)[elasticsearch-service]no longer reports a version mismatchkibana-ci/elasticsearch-serverlessMade with Cursor