Skip to content

[Deployment Agnostic] Adding registryUrl configuration for DA tests#221628

Merged
yngrdyn merged 2 commits intoelastic:mainfrom
yngrdyn:registryUrl-for-deployment-agnostic-tests
May 27, 2025
Merged

[Deployment Agnostic] Adding registryUrl configuration for DA tests#221628
yngrdyn merged 2 commits intoelastic:mainfrom
yngrdyn:registryUrl-for-deployment-agnostic-tests

Conversation

@yngrdyn
Copy link
Contributor

@yngrdyn yngrdyn commented May 27, 2025

When introducing package registry configuration in #193144 I missed the set up of xpack.fleet.registryUrl which has resulted in flaky tests whenever the test uses fleet underneath.

@yngrdyn yngrdyn requested a review from a team as a code owner May 27, 2025 14:20
@yngrdyn yngrdyn changed the title [Dataset quality] Adding registryUrl configuration for DA tests Adding registryUrl configuration for DA tests May 27, 2025
@yngrdyn yngrdyn changed the title Adding registryUrl configuration for DA tests [Deployment Agnostic] Adding registryUrl configuration for DA tests May 27, 2025
@yngrdyn yngrdyn added release_note:skip Skip the PR/issue when compiling release notes backport This PR is a backport of another PR v8.19.0 v9.0.0 v9.1.0 labels May 27, 2025
Copy link
Contributor

@MiriamAparicio MiriamAparicio left a comment

Choose a reason for hiding this comment

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

Thanks for the fix 🌟

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

@elasticmachine
Copy link
Contributor

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

✅ unchanged

@yngrdyn yngrdyn merged commit 1a5ba16 into elastic:main May 27, 2025
10 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.19, 9.0

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

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.19 Backport failed because of merge conflicts
9.0 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

node scripts/backport --pr 221628

Questions ?

Please refer to the Backport tool documentation

This was referenced May 28, 2025
akowalska622 pushed a commit to akowalska622/kibana that referenced this pull request May 29, 2025
…lastic#221628)

When introducing package registry configuration in
elastic#193144 I missed the set up of
`xpack.fleet.registryUrl` which has resulted in flaky tests whenever the
test uses fleet underneath.
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label May 29, 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 221628 locally
cc: @yngrdyn

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 221628 locally
cc: @yngrdyn

@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 221628 locally
cc: @yngrdyn

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 221628 locally
cc: @yngrdyn

@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 221628 locally
cc: @yngrdyn

@yngrdyn
Copy link
Contributor Author

yngrdyn commented Jun 5, 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

@yngrdyn yngrdyn removed the v9.0.0 label Jun 5, 2025
yngrdyn added a commit that referenced this pull request Jun 5, 2025
…tests (#221628) (#222736)

# Backport

This will backport the following commits from `main` to `8.19`:
- [[Deployment Agnostic] Adding registryUrl configuration for DA tests
(#221628)](#221628)

<!--- Backport version: 10.0.0 -->

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

<!--BACKPORT [{"author":{"name":"Yngrid
Coello","email":"yngrid.coello@elastic.co"},"sourceCommit":{"committedDate":"2025-05-27T17:14:24Z","message":"[Deployment
Agnostic] Adding registryUrl configuration for DA tests
(#221628)\n\nWhen introducing package registry configuration
in\nhttps://github.com//pull/193144 I missed the set up
of\n`xpack.fleet.registryUrl` which has resulted in flaky tests whenever
the\ntest uses fleet
underneath.","sha":"1a5ba164838a212ded3760afb0a932f7d208cf11","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:skip","backport
missing","v9.0.0","v9.1.0","v8.19.0"],"title":"[Deployment Agnostic]
Adding registryUrl configuration for DA
tests","number":221628,"url":"https://github.com/elastic/kibana/pull/221628","mergeCommit":{"message":"[Deployment
Agnostic] Adding registryUrl configuration for DA tests
(#221628)\n\nWhen introducing package registry configuration
in\nhttps://github.com//pull/193144 I missed the set up
of\n`xpack.fleet.registryUrl` which has resulted in flaky tests whenever
the\ntest uses fleet
underneath.","sha":"1a5ba164838a212ded3760afb0a932f7d208cf11"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.19"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221628","number":221628,"mergeCommit":{"message":"[Deployment
Agnostic] Adding registryUrl configuration for DA tests
(#221628)\n\nWhen introducing package registry configuration
in\nhttps://github.com//pull/193144 I missed the set up
of\n`xpack.fleet.registryUrl` which has resulted in flaky tests whenever
the\ntest uses fleet
underneath.","sha":"1a5ba164838a212ded3760afb0a932f7d208cf11"}},{"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 5, 2025
@tonyghiani
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
9.0

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

Questions ?

Please refer to the Backport tool documentation

tonyghiani pushed a commit to tonyghiani/kibana that referenced this pull request Jul 15, 2025
…lastic#221628)

When introducing package registry configuration in
elastic#193144 I missed the set up of
`xpack.fleet.registryUrl` which has resulted in flaky tests whenever the
test uses fleet underneath.

(cherry picked from commit 1a5ba16)

# Conflicts:
#	x-pack/test/api_integration/deployment_agnostic/default_configs/serverless.config.base.ts
#	x-pack/test/api_integration/deployment_agnostic/default_configs/stateful.config.base.ts
tonyghiani added a commit that referenced this pull request Jul 15, 2025
…ests (#221628) (#227942)

# Backport

Closes #205017

This will backport the following commits from `main` to `9.0`:
- [[Deployment Agnostic] Adding registryUrl configuration for DA tests
(#221628)](#221628)

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

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

<!--BACKPORT [{"author":{"name":"Yngrid
Coello","email":"yngrid.coello@elastic.co"},"sourceCommit":{"committedDate":"2025-05-27T17:14:24Z","message":"[Deployment
Agnostic] Adding registryUrl configuration for DA tests
(#221628)\n\nWhen introducing package registry configuration
in\nhttps://github.com//pull/193144 I missed the set up
of\n`xpack.fleet.registryUrl` which has resulted in flaky tests whenever
the\ntest uses fleet
underneath.","sha":"1a5ba164838a212ded3760afb0a932f7d208cf11","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["backport","release_note:skip","v9.1.0","v8.19.0"],"title":"[Deployment
Agnostic] Adding registryUrl configuration for DA
tests","number":221628,"url":"https://github.com/elastic/kibana/pull/221628","mergeCommit":{"message":"[Deployment
Agnostic] Adding registryUrl configuration for DA tests
(#221628)\n\nWhen introducing package registry configuration
in\nhttps://github.com//pull/193144 I missed the set up
of\n`xpack.fleet.registryUrl` which has resulted in flaky tests whenever
the\ntest uses fleet
underneath.","sha":"1a5ba164838a212ded3760afb0a932f7d208cf11"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221628","number":221628,"mergeCommit":{"message":"[Deployment
Agnostic] Adding registryUrl configuration for DA tests
(#221628)\n\nWhen introducing package registry configuration
in\nhttps://github.com//pull/193144 I missed the set up
of\n`xpack.fleet.registryUrl` which has resulted in flaky tests whenever
the\ntest uses fleet
underneath.","sha":"1a5ba164838a212ded3760afb0a932f7d208cf11"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/222736","number":222736,"state":"MERGED","mergeCommit":{"sha":"739d2abeedf4604c2c37b14c04263a2b370455a5","message":"[8.19]
[Deployment Agnostic] Adding registryUrl configuration for DA tests
(#221628) (#222736)\n\n# Backport\n\nThis will backport the following
commits from `main` to `8.19`:\n- [[Deployment Agnostic] Adding
registryUrl configuration for DA
tests\n(#221628)](https://github.com/elastic/kibana/pull/221628)\n\n\n\n###
Questions ?\nPlease refer to the [Backport
tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by:
Dzmitry Lemechko <dzmitry.lemechko@elastic.co>"}}]}] BACKPORT-->

Co-authored-by: Yngrid Coello <yngrid.coello@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR release_note:skip Skip the PR/issue when compiling release notes v8.19.0 v9.0.4 v9.1.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants