CI builds ES revision from sources based on es-version file#875
Merged
CI builds ES revision from sources based on es-version file#875
Conversation
Contributor
NickDris
commented
Oct 3, 2025
- Github workflows now execute CI with the additional --revision option, effectively building a specific revision of Elasticsearch from sources
- es-version added to root directory which determine what is the value of the --revision argument that will be used in CI.
- Github workflows now execute CI with the additional --revision option, effectively building a specific revision of Elasticsearch from sources - es-version added to root directory which determine what is the value of the --revision argument that will be used in CI.
gbanasiak
approved these changes
Oct 6, 2025
NickDris
added a commit
to NickDris/rally-tracks
that referenced
this pull request
Oct 7, 2025
) - 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.
NickDris
added a commit
to NickDris/rally-tracks
that referenced
this pull request
Oct 7, 2025
* Tests tracks selectively based on PR changes (elastic#858) 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. * CI builds ES revision from sources based on es-version file (elastic#875) - 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.
NickDris
added a commit
to NickDris/rally-tracks
that referenced
this pull request
Oct 7, 2025
* Tests tracks selectively based on PR changes (elastic#858) 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. * CI builds ES revision from sources based on es-version file (elastic#875) - 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.
NickDris
added a commit
that referenced
this pull request
Oct 7, 2025
…ORT (#875) --> - 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.
Collaborator
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Collaborator
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Collaborator
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
Collaborator
💔 All backports failed
Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
NickDris
added a commit
that referenced
this pull request
Oct 13, 2025
- 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.
NickDris
added a commit
that referenced
this pull request
Oct 13, 2025
…) (#886) - 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.
gbanasiak
pushed a commit
to gbanasiak/rally-tracks
that referenced
this pull request
Dec 5, 2025
) - 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.
NickDris
added a commit
to NickDris/rally-tracks
that referenced
this pull request
Dec 10, 2025
) - 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.
NickDris
added a commit
that referenced
this pull request
Dec 12, 2025
- 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.
NickDris
added a commit
to NickDris/rally-tracks
that referenced
this pull request
Dec 18, 2025
) - 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.
NickDris
added a commit
that referenced
this pull request
Dec 20, 2025
* Tests tracks selectively based on PR changes (#858) * CI builds ES revision from sources based on es-version file (#875) * Drop Python 3.9 and introduce Python 3.13 in CI (#877) * [ES-13188] Update GH macOS hosted runner image (#883) * Address pytest deprecations (#911) * CI determines Elasticsearch build arguments using unified job in gh workflow [stateful] (#925) * Fix an error where ci arguments were not applied properly (#928) * 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 * Add backport reminder and reorganize the backporting actions. (#889) * Rename IT folders (#938) * Fix pytest skip argument (#905) * Backport reminders - fix missing default values in workflow (#947) * Upgrade pip to 25.2 * Fix conflict in it_tracks * Update deprecated gh actions * Track changes for 8.19 * Fix test job which does not require the output of other jobs * Add backport reminder and reorganize the backporting actions. (#889) * Fix an error where ci arguments were not applied properly (#928) * Reduce filtering scope in CI workflow (#908) * Add pytest marker for cars * Address merge conflicts * Run serverless CI only on PRs targeting master (#859) * Accept pragma risks for joins esql * Make esql-full-text-functions a snapshot_only_challenge * Set index template for ingest_mode: data_stream (#849)
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
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.