Skip to content

[8.15] Restore CI operations#949

Merged
gbanasiak merged 18 commits intoelastic:8.15from
gbanasiak:restore-ci
Dec 8, 2025
Merged

[8.15] Restore CI operations#949
gbanasiak merged 18 commits intoelastic:8.15from
gbanasiak:restore-ci

Conversation

@gbanasiak
Copy link
Contributor

@gbanasiak gbanasiak commented Dec 5, 2025

Refreshes 8.15 branch to match latest CI setup.

NickDris and others added 17 commits December 5, 2025 13:05
Implements test execution based on PR changes by integrating
pytest-rally plugin's --track-filter option. Tests will now only run
for tracks affected by changes in the top-level directories of the
repository.

- Updates test command configurations to support dynamic track
filtering arguments
- Adds pytest track markers to associate test classes and methods
 with specific tracks
- Implements CI workflow changes to detect changed tracks and
pass them as filter arguments
- Defines RUN_FULL_CI_WHEN_CHANGED env variable which
point to files that when changed full CI is executed.
)

- Github workflows now execute CI with the additional --revision
option, effectively building Elasticsearch from sources using 
a revision SHA and according to [Rally --revision rules](https://esrally.readthedocs.io/en/stable/command_line_reference.html#revision)
- es-version added to root directory which determine what is the
value of the --revision argument that will be used in CI.
…orkflow [stateful] (elastic#925)

- determine-es-revision job was changed to determine-es-build job
that now configures the --source-build-release argument together with
the --revision argument if the es-version file contents is equal to
'latest' or 'current'
- show determined arguments in the respective jobs for easy debug
* Fix an error where ci arguments were not applied properly

* Test the change

* Test failed retry with another fix

* Previous fix failed retry

* Revert es-version to current

* Keep the indents if if/else
…c#889)

Refactored backport cli to include all requirements existing at the moment for 
automated backporting of PRs. 

Supporting label and remind commands and --dry-run for testing.
@gbanasiak gbanasiak marked this pull request as ready for review December 5, 2025 15:48
@gbanasiak gbanasiak requested a review from NickDris December 5, 2025 15:48
Copy link
Contributor

@NickDris NickDris left a comment

Choose a reason for hiding this comment

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

LGTM.
I left a minor comment for modification, which is non-blocking because backporting only concerns master branch.

)

After merging backport PR we noticed workflow failures 
because of missing values for --lookback-days 
and --pending-reminder-age-days. Also --pr-mode arg 
was incorrectly placed in the single PR case.
@gbanasiak gbanasiak merged commit fd4969d into elastic:8.15 Dec 8, 2025
14 checks passed
@gbanasiak gbanasiak deleted the restore-ci branch December 8, 2025 15:54
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 9, 2025
@esbenchmachine
Copy link
Collaborator

@gbanasiak
A backport is pending for this PR. Please add all required vX.Y version labels.

  • If it is intended for the current Elasticsearch release version, apply the corresponding version label.
  • If it also supports past released versions, add those labels too.
  • If it only targets a future version, wait until that version label exists and then add it.
    (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure backport PRs have backport label and are passing tests.
  3. Merge backport PRs (you can approve yourself and enable auto-merge).
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

@gbanasiak gbanasiak added backport This PR is a backport of some other PR and removed backport pending Awaiting backport to stable release branch labels Dec 9, 2025
@NickDris NickDris mentioned this pull request Dec 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of some other PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants