Skip to content

[8.19] [ML] Make Appex QA/PyTorch tests version-aware on release branches (#3115) - #3118

Merged
edsavage merged 1 commit into
elastic:8.19from
edsavage:backport/8.19/qa-pytorch-stack-version
Jul 28, 2026
Merged

[8.19] [ML] Make Appex QA/PyTorch tests version-aware on release branches (#3115)#3118
edsavage merged 1 commit into
elastic:8.19from
edsavage:backport/8.19/qa-pytorch-stack-version

Conversation

@edsavage

Copy link
Copy Markdown
Contributor

Backport of #3115 to 8.19 (hand-adapted for 8.19's trigger scripts). Derives STACK_VERSION=8.19.20 / ES_BRANCH=8.19 so the Appex QA/PyTorch downstream finds the ml-cpp-8.19.20-SNAPSHOT artifact instead of main's 9.6.0-SNAPSHOT.

Made with Cursor

Backport of elastic#3115, adapted for 8.19's trigger scripts (raw BUILDKITE_MESSAGE,
build_test_* depends_on). Derives STACK_VERSION/ES_BRANCH so the downstream QA
build finds the ml-cpp-8.19.20-SNAPSHOT artifact instead of main's SNAPSHOT.

Co-authored-by: Cursor <[email protected]>
@elasticsearchmachine

Copy link
Copy Markdown

Pinging @elastic/ml-core (Team:ML)

@edsavage

Copy link
Copy Markdown
Contributor Author

Closing this manually-created backport. It will be recreated automatically by the auto-backport workflow when the source PR #3115 merges (source now carries the auto-backport + version labels).

@edsavage edsavage closed this Jul 27, 2026
@edsavage edsavage reopened this Jul 27, 2026
@edsavage

Copy link
Copy Markdown
Contributor Author

buildkite build

@edsavage
edsavage enabled auto-merge (squash) July 27, 2026 23:04
@edsavage edsavage changed the title [8.19] [ML] Make Appex QA/PyTorch tests version-aware on release branches [8.19] [ML] Make Appex QA/PyTorch tests version-aware on release branches (#3115) Jul 27, 2026
@edsavage

Copy link
Copy Markdown
Contributor Author

buildkite build

@edsavage
edsavage merged commit f714770 into elastic:8.19 Jul 28, 2026
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants