[ML] Skip Java ES integration tests for version-bump PRs (9.4)#3087
Merged
Conversation
Backport the ci:skip-es-tests / version-bump topic-branch detection from the minor-version-bump automation (elastic#3064) so automated patch version-bump PRs on this release branch skip the Java ES integration test pipelines. These tests cannot resolve the ml-cpp SNAPSHOT dependency after a version bump (the ES branch still references the previous patch), so they fail spuriously on what are metadata-only changes. The PR pipeline is generated from the checked-out branch, so this gating must exist on each release branch that receives automated version bumps. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backports the
ci:skip-es-tests/ version-bump topic-branch detection from the minor-version-bump automation (#3064) to the9.4release branch.Automated patch version-bump PRs on release branches currently run the Java ES integration test pipelines, which fail spuriously: after the bump the ES branch still references the previous ml-cpp
SNAPSHOT, so the build cannot resolve the dependency (e.g.Could not find org.elasticsearch.ml:ml-cpp:9.4.4-SNAPSHOTin ml-cpp-pr-builds #2825). The PR pipeline is generated from the checked-out branch, so the skip logic must exist on each release branch that receives version bumps — it is present onmain/9.5but was missing here.Changes (CI-only, self-contained):
.buildkite/ml_pipeline/config.py: addskip_version_bump_pr_ci(set by theci:skip-es-testslabel or aci/ml-cpp-version-bump-*/ci/ml-cpp-minor-freeze-main-*topic branch)..buildkite/pipeline.json.py: gate the ES-test upload steps onnot config.skip_version_bump_pr_ci.Test plan
pipeline.json.pygenerator: normal PR build keeps all ES-test steps; a version-bump branch (or theci:skip-es-testslabel) produces zero ES-test steps.9.4that the Java ES IT steps no longer appear.Made with Cursor