Skip to content

Conversation

ldematte
Copy link
Contributor

Re-introduce #128614, fixing how we invoke CURL on the manifest URL

@ldematte ldematte requested a review from a team as a code owner June 17, 2025 09:32
@ldematte ldematte added >non-issue :Delivery/Build Build or test infrastructure auto-backport Automatically create backport pull requests when merged v9.1.0 v9.0.3 labels Jun 17, 2025
@ldematte ldematte requested a review from a team June 17, 2025 09:32
@elasticsearchmachine elasticsearchmachine added the Team:Delivery Meta label for Delivery team label Jun 17, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

1 similar comment
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-delivery (Team:Delivery)

@ldematte
Copy link
Contributor Author

ldematte added 2 commits June 17, 2025 13:44
…e/elasticsearch into bc-upgrade/bc-commit-hash-script
A new bc-upgrade step in the intake pipeline invokes a bash script to get the commit hash of the latest BC (or snapshot if no BC is available yet) from https://docs.elastic.dev/release/stack/release-api#future-releases for the current branch and runs BWC / upgrade tests from this commit to the HEAD commit of the current branch. If no matching BC / snapshot exists, the upgrade tests are skipped. Relates to ES-11905 # Conflicts: #	.buildkite/scripts/run-bc-upgrade-tests.sh
Copy link
Contributor

@prdoyle prdoyle left a comment

Choose a reason for hiding this comment

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

A couple of optional comments...

@ldematte ldematte enabled auto-merge (squash) June 17, 2025 14:22
@ldematte ldematte merged commit 796d659 into elastic:main Jun 18, 2025
27 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
9.0 Commit could not be cherrypicked due to conflicts

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

@ldematte ldematte deleted the bc-upgrade/bc-commit-hash-script branch June 18, 2025 09:02
@ldematte
Copy link
Contributor Author

Already backported in #129522

kderusso pushed a commit to kderusso/elasticsearch that referenced this pull request Jun 23, 2025
…29532) A new bc-upgrade step in the intake pipeline invokes a bash script to get the commit hash of the latest BC (or snapshot if no BC is available yet) from https://docs.elastic.dev/release/stack/release-api#future-releases for the current branch and runs BWC / upgrade tests from this commit to the HEAD commit of the current branch. If no matching BC / snapshot exists, the upgrade tests are skipped. Relates to ES-11905
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 :Delivery/Build Build or test infrastructure >non-issue Team:Delivery Meta label for Delivery team v9.0.3 v9.1.0

5 participants