Skip to content

Split up bc and pr upgrade tests #129756

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Jun 23, 2025
Merged

Conversation

breskeby
Copy link
Contributor

@breskeby breskeby commented Jun 20, 2025

This splits and groups the bcUpgradeTest tasks in ci to run more in parallel and reduce overall pull-request ci build duration

Relates to ES-12145

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

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

@breskeby breskeby force-pushed the split-bcUpgradeTest branch from ee01686 to 8485c96 Compare June 20, 2025 14:47
@breskeby breskeby requested review from ldematte and jozala June 21, 2025 07:45
Copy link
Contributor

@ldematte ldematte left a comment

Choose a reason for hiding this comment

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

Changes look good to me, but you may want the opinion of someone better versed in gradle/buildkite

@breskeby breskeby merged commit f1b2c8d into elastic:main Jun 23, 2025
32 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

The backport operation could not be completed due to the following error:

There are no branches to backport to. Aborting.

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

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 backport pending :Delivery/Build Build or test infrastructure >non-issue Team:Delivery Meta label for Delivery team v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants