Skip to content

[FTR] add feature flags configs for deployment-agnostic tests#222371

Merged
dmlemeshko merged 8 commits intoelastic:mainfrom
dmlemeshko:ftr/create-DA-feature-flag-configs
Jun 4, 2025
Merged

[FTR] add feature flags configs for deployment-agnostic tests#222371
dmlemeshko merged 8 commits intoelastic:mainfrom
dmlemeshko:ftr/create-DA-feature-flag-configs

Conversation

@dmlemeshko
Copy link
Contributor

@dmlemeshko dmlemeshko commented Jun 3, 2025

Relocating tests added in #221139 into separate feature flag configs, that are not run on MKI but only Kibana CI.

dmlemeshko and others added 2 commits June 3, 2025 15:59
…t --include-path /api/status --include-path /api/alerting/rule/ --include-path /api/alerting/rules --include-path /api/actions --include-path /api/security/role --include-path /api/spaces --include-path /api/streams --include-path /api/fleet --include-path /api/dashboards --include-path /api/saved_objects/_import --include-path /api/saved_objects/_export --include-path /api/maintenance_window --update'
@dmlemeshko dmlemeshko changed the title [FTR] add FTR configs to feature flags tests in deployment-agnostic setup [FTR] add feature flags configs for deployment-agnostic tests Jun 3, 2025
export default createServerlessFeatureFlagTestConfig({
serverlessProject: 'oblt',
kbnServerArgs: [
'--xpack.actions.preconfigured',
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we need an async function getTlsWebhookServerUrls call to set this argument, I put the logic in helper method called inside createServerlessFeatureFlagTestConfig.

@dmlemeshko dmlemeshko self-assigned this Jun 4, 2025
@dmlemeshko dmlemeshko added release_note:skip Skip the PR/issue when compiling release notes backport:version Backport to applied version labels v9.1.0 v8.19.0 labels Jun 4, 2025
@dmlemeshko dmlemeshko marked this pull request as ready for review June 4, 2025 09:49
@dmlemeshko dmlemeshko requested review from a team as code owners June 4, 2025 09:49
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

✅ unchanged

History

cc @dmlemeshko

Copy link
Member

@pheyos pheyos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@cesco-f cesco-f left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@dmlemeshko dmlemeshko merged commit 966f734 into elastic:main Jun 4, 2025
19 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.19

https://github.com/elastic/kibana/actions/runs/15444290529

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.19 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.19:
- [ska][x-pack] relocate platform & solutions tests [6] (#220612)
- [Deployment Agnostic] Adding registryUrl configuration for DA tests (#221628)

Manual backport

To create the backport manually run:

node scripts/backport --pr 222371

Questions ?

Please refer to the Backport tool documentation

zacharyparikh pushed a commit to zacharyparikh/kibana that referenced this pull request Jun 4, 2025
…c#222371)

Relocating tests added in elastic#221139 into separate feature flag configs,
that are not run on MKI but only Kibana CI.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jun 6, 2025
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

1 similar comment
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

2 similar comments
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

nickpeihl pushed a commit to nickpeihl/kibana that referenced this pull request Jun 12, 2025
…c#222371)

Relocating tests added in elastic#221139 into separate feature flag configs,
that are not run on MKI but only Kibana CI.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

3 similar comments
@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

@kibanamachine
Copy link
Contributor

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 222371 locally
cc: @dmlemeshko

@pheyos
Copy link
Member

pheyos commented Jun 19, 2025

💚 All backports created successfully

Status Branch Result
8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

@kibanamachine
Copy link
Contributor

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.
cc: @dmlemeshko

pheyos added a commit that referenced this pull request Jun 20, 2025
…222371) (#224588)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[FTR] add feature flags configs for deployment-agnostic tests
(#222371)](#222371)

Also cherry-picked a few required changes from #218725 which was not
backported.

<!--- Backport version: 10.0.1 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-06-04T13:57:03Z","message":"[FTR]
add feature flags configs for deployment-agnostic tests
(#222371)\n\nRelocating tests added in #221139 into separate feature
flag configs,\nthat are not run on MKI but only Kibana
CI.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"966f73481d6cfb25c59f363149e302b9b9fa40a2","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","backport:version","v9.1.0","v8.19.0"],"title":"[FTR] add
feature flags configs for deployment-agnostic
tests","number":222371,"url":"https://github.com/elastic/kibana/pull/222371","mergeCommit":{"message":"[FTR]
add feature flags configs for deployment-agnostic tests
(#222371)\n\nRelocating tests added in #221139 into separate feature
flag configs,\nthat are not run on MKI but only Kibana
CI.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"966f73481d6cfb25c59f363149e302b9b9fa40a2"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/222371","number":222371,"mergeCommit":{"message":"[FTR]
add feature flags configs for deployment-agnostic tests
(#222371)\n\nRelocating tests added in #221139 into separate feature
flag configs,\nthat are not run on MKI but only Kibana
CI.\n\n---------\n\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"966f73481d6cfb25c59f363149e302b9b9fa40a2"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jun 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels release_note:skip Skip the PR/issue when compiling release notes v8.19.0 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants