Currently the "install Elasticsearch" step in the CI takes a long time - sometimes in excess of 10 minutes:
Tue, 17 Mar 2026 12:30:54 GMT
INFO pytest_rally.elasticsearch:elasticsearch.py:97 Installing Elasticsearch: [esrally install --quiet --http-port=19200 --node=rally-node --master-nodes=rally-node --car=4gheap,trial-license,x-pack-ml,lean-watermarks --seed-hosts="127.0.0.1:19300" --revision=current]
Tue, 17 Mar 2026 12:40:48 GMT
INFO pytest_rally.elasticsearch:elasticsearch.py:106 Starting Elasticsearch: [esrally start --runtime-jdk=bundled --installation-id=bde8671e-61c0-4308-9ef9-31986608c520 --race-id=9b5f4e64-a34d-4cc2-862c-54a619a1c402]
For most PRs in rally and rally-tracks; we don't necessarily need the very latest elasticsearch@main commit, having the most recent snapshot is good enough.
Suggestion:
- Investigate using the latest snapshot instead of building from source.
- Allow a label to be provided for the cases where a new feature that is in main, but not yet in a snapshot build is required, that would allow the build method to be used instead
Currently the "install Elasticsearch" step in the CI takes a long time - sometimes in excess of 10 minutes:
For most PRs in rally and rally-tracks; we don't necessarily need the very latest elasticsearch@main commit, having the most recent snapshot is good enough.
Suggestion: