Skip to content

Trim unnecessary ITs#809

Merged
gbanasiak merged 3 commits intoelastic:masterfrom
gbanasiak:trim-unnecessary-it
Jul 16, 2025
Merged

Trim unnecessary ITs#809
gbanasiak merged 3 commits intoelastic:masterfrom
gbanasiak:trim-unnecessary-it

Conversation

@gbanasiak
Copy link
Contributor

This removes unused stateful Buildkite pipeline, and changes serverless pipeline to be only triggered by Buildkite PR bot (via API). Serverless tests only make sense when run against master branch so this gets narrowed down too.

@gbanasiak gbanasiak requested a review from a team July 8, 2025 08:20
@gbanasiak gbanasiak merged commit 581478b into elastic:master Jul 16, 2025
13 checks passed
@gbanasiak gbanasiak deleted the trim-unnecessary-it branch July 16, 2025 06:33
@esbenchmachine
Copy link
Collaborator

💔 All backports failed

Status Branch Result
8.15 Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

backport --pr 809

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

@gbanasiak
Copy link
Contributor Author

💚 All backports created successfully

Status Branch Result
8.15

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

Questions ?

Please refer to the Backport tool documentation

gbanasiak added a commit that referenced this pull request Jul 18, 2025
(cherry picked from commit 581478b)

# Conflicts:
#	catalog-info.yaml
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 19, 2025
@esbenchmachine
Copy link
Collaborator

@gbanasiak
A backport is pending for this PR. Please add all required vX.Y version labels.

  • If it is intended for the current Elasticsearch release version, apply the corresponding version label.
  • If it also supports past released versions, add those labels too.
  • If it only targets a future version, wait until that version label exists and then add it.
    (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure backport PRs have backport label and are passing tests.
  3. Merge backport PRs (you can approve yourself and enable auto-merge).
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments