Skip to content

[9.5] [ML] Make Appex QA/PyTorch tests version-aware on release branches#3116

Open
edsavage wants to merge 1 commit into
elastic:9.5from
edsavage:backport/9.5/qa-pytorch-stack-version
Open

[9.5] [ML] Make Appex QA/PyTorch tests version-aware on release branches#3116
edsavage wants to merge 1 commit into
elastic:9.5from
edsavage:backport/9.5/qa-pytorch-stack-version

Conversation

@edsavage

Copy link
Copy Markdown
Contributor

Backport of #3115 to 9.5.

Makes the Appex QA/PyTorch downstream trigger pass STACK_VERSION/ES_BRANCH derived from this build (9.5.0 / 9.5) so the downstream finds the ml-cpp-9.5.0-SNAPSHOT artifact instead of defaulting to main's 9.6.0-SNAPSHOT.

This PR also serves as the live end-to-end test: ci:run-pytorch-tests will be applied so the 9.5 build exercises the downstream QA pytorch pipeline with the fix in place.

Made with Cursor

The downstream appex-qa-stateful-custom-ml-cpp-build-testing pipeline
(elastic/qaf-tests) defaults to ES_BRANCH=main and STACK_VERSION=<current
main SNAPSHOT>, then downloads ml-cpp-<version>-SNAPSHOT-linux-x86_64.zip
from the parent build. On a release-branch / backport build the parent
produced ml-cpp-<release-version>-SNAPSHOT-... instead, so the download
missed ('No artifacts found') and the QA/PyTorch build failed spuriously
(e.g. a 9.5 backport looking for 9.6.0-SNAPSHOT).

Derive STACK_VERSION from gradle.properties (the exact artifact version)
and ES_BRANCH by comparing to ml-cpp main's version (main for the current
dev line, else major.minor), and forward both through the QA and PyTorch
downstream triggers. For main builds the derived values equal today's
defaults, so only release-branch/backport builds change behaviour. No
qaf-tests change is required; it already supports these overrides and lists
the active release branches/versions.

Co-authored-by: Cursor <cursoragent@cursor.com>
@edsavage

Copy link
Copy Markdown
Contributor Author

buildkite build

@elasticsearchmachine

Copy link
Copy Markdown

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

@edsavage

Copy link
Copy Markdown
Contributor Author

buildkite run_pytorch_tests

@edsavage

Copy link
Copy Markdown
Contributor Author

buildkite build

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