Skip to content

Migrate x-pack core module to new testing framework #125740

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 27, 2025

Conversation

mark-vieira
Copy link
Contributor

Converts :x-pack:plugin:core to new testing framework.

@mark-vieira mark-vieira added >test Issues or PRs that are addressing/adding tests :Delivery/Build Build or test infrastructure >refactoring auto-backport Automatically create backport pull requests when merged v8.18.1 v8.19.0 v9.0.1 labels Mar 26, 2025
@mark-vieira mark-vieira requested a review from a team as a code owner March 26, 2025 23:11
@elasticsearchmachine elasticsearchmachine added v9.1.0 Team:Delivery Meta label for Delivery team labels Mar 26, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

requiresFeature 'es.failure_store_feature_flag_enabled', Version.fromString("8.15.0")
systemProperty 'es.queryable_built_in_roles_enabled', 'false'
tasks.named("javaRestTest") {
usesDefaultDistribution("uses the _xpack api")
Copy link
Contributor Author

Choose a reason for hiding this comment

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

From what I can tell this tries to resolve pretty much every x-pack module so I gave up on going down this rabbit hole. Fortunately, these tests suites are pretty light weight so it's not a big deal.

# Conflicts:
#	build-tools-internal/src/main/java/org/elasticsearch/gradle/internal/RestrictedBuildApiService.java
@mark-vieira mark-vieira merged commit 0c50403 into elastic:main Mar 27, 2025
17 checks passed
mark-vieira added a commit to mark-vieira/elasticsearch that referenced this pull request Mar 27, 2025
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.18
8.x Commit could not be cherrypicked due to conflicts
9.0 Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 125740

@mark-vieira
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.x
9.0

Questions ?

Please refer to the Backport tool documentation

mark-vieira added a commit to mark-vieira/elasticsearch that referenced this pull request Mar 28, 2025
elasticsearchmachine pushed a commit that referenced this pull request Mar 28, 2025
elasticsearchmachine pushed a commit that referenced this pull request Mar 28, 2025
omricohenn pushed a commit to omricohenn/elasticsearch that referenced this pull request Mar 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged :Delivery/Build Build or test infrastructure >refactoring Team:Delivery Meta label for Delivery team >test Issues or PRs that are addressing/adding tests v8.18.1 v8.19.0 v9.0.1 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants