Skip to content

Conversation

@mosche
Copy link
Contributor

@mosche mosche commented Oct 16, 2025

Relates to ES-11813

@mosche mosche requested a review from a team October 16, 2025 12:46
@mosche mosche requested a review from a team as a code owner October 16, 2025 12:46
@mosche mosche added >test Issues or PRs that are addressing/adding tests >refactoring labels Oct 16, 2025
@elasticsearchmachine elasticsearchmachine added needs:triage Requires assignment of a team area label v9.3.0 labels Oct 16, 2025
}

artifacts {
restXpackTests(new File(projectDir, "src/yamlRestTest/resources/rest-api-spec/test"))
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mark-vieira I'm not sure about this change. This folder contains now both specs with and without security, previously it was just the ones without. Is there a way to filter these?

Copy link
Contributor

Choose a reason for hiding this comment

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

No, we expect a 1 project - 1 artifact type mapping here. You can filter them on the consumer side though when setting up your rest test.

@mosche mosche added :Core/Infra/Core Core issues without another label and removed needs:triage Requires assignment of a team area label labels Oct 16, 2025
@elasticsearchmachine elasticsearchmachine added the Team:Core/Infra Meta label for core/infra team label Oct 16, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@mosche mosche added auto-backport Automatically create backport pull requests when merged v9.2.1 labels Oct 16, 2025
@mosche mosche self-assigned this Oct 16, 2025
@mosche mosche merged commit 79791c8 into elastic:main Oct 23, 2025
34 checks passed
mosche added a commit to mosche/elasticsearch that referenced this pull request Oct 23, 2025
mosche added a commit to mosche/elasticsearch that referenced this pull request Oct 23, 2025
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
9.2
8.19 Commit could not be cherrypicked due to conflicts
9.1

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

elasticsearchmachine pushed a commit that referenced this pull request Oct 23, 2025
mosche added a commit to mosche/elasticsearch that referenced this pull request Oct 24, 2025
Relates to ES-11813

(cherry picked from commit 79791c8)

# Conflicts:
#	x-pack/plugin/watcher/qa/rest/build.gradle
@mosche
Copy link
Contributor Author

mosche commented Oct 24, 2025

💚 All backports created successfully

Status Branch Result
8.19

Questions ?

Please refer to the Backport tool documentation

elasticsearchmachine pushed a commit that referenced this pull request Oct 24, 2025
…37046)

* Migrate watcher REST tests to new test framework. (#136690)

Relates to ES-11813

* fix build
elasticsearchmachine pushed a commit that referenced this pull request Oct 24, 2025
…137087)

* Migrate watcher REST tests to new test framework. (#136690)

Relates to ES-11813

(cherry picked from commit 79791c8)

# Conflicts:
#	x-pack/plugin/watcher/qa/rest/build.gradle

* fix rest compat test

* fix
fzowl pushed a commit to voyage-ai/elasticsearch that referenced this pull request Nov 3, 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 backport pending :Core/Infra/Core Core issues without another label >refactoring Team:Core/Infra Meta label for core/infra team >test Issues or PRs that are addressing/adding tests v8.19.7 v9.1.7 v9.2.1 v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants