Conversation
| [tool.hatch.version] | ||
| path = "esrally/_version.py" | ||
| source = "vcs" | ||
| [tool.hatch.version.raw-options] | ||
| local_scheme = "no-local-version" | ||
| [tool.hatch.build.hooks.vcs] | ||
| version-file = "esrally/_version.py" |
There was a problem hiding this comment.
This instructs hatch and hatch-vcs to create the esrally/_version.py file, using numbers like devN instead of the git hash, as this is the only format that PyPI supports.
There was a problem hiding this comment.
Add it as a comment. It will help in the future.
|
The rally-tracks-compat failure where Rally cannot read its own version: Stack trace |
|
The new error is that the version is set to |
fressi-elastic
left a comment
There was a problem hiding this comment.
Thank you so much for this!
It would very nice having more comments in the code to explain a bit what is happening. Please make sure this works after typing make install or after installing it using pip.
fressi-elastic
left a comment
There was a problem hiding this comment.
Please rebase on top of master branch.
gbanasiak
left a comment
There was a problem hiding this comment.
Cosmetic question:
% esrally --version
esrally 2.13.1.dev7 (git revision: df58675e2121872efc21e6191a97df153fc3ce42)
How is this version calculated? Is this the version from the last tag auto-incremented + devN where N is the commit number from the tag? Historically, we went for <last-version>.dev format because we didn't know what will be the next version. Could we replicate "last version" logic with hatch-vcs?
| *.egg-info/ | ||
| .installed.cfg | ||
| *.egg | ||
| esrally/_version.py # hatch-vcs |
There was a problem hiding this comment.
There are no inline comments in .gitignore, please move the comment to the previous line.
| # Wipe away any lingering caches, copied over from the local machine | ||
| RUN find /rally -name "__pycache__" -exec rm -rf -- \{\} \; 2>/dev/null || true | ||
| RUN find /rally -name ".pyc" -exec rm -rf -- \{\} \; 2>/dev/null || true | ||
| ENV SETUPTOOLS_SCM_PRETEND_VERSION=${RALLY_VERSION} |
There was a problem hiding this comment.
In dev Docker scripts RALLY_VERSION has unexpected value, see this failure in a test build:
`vcs`: Invalid version: 'refs_pull_2080_head-df58675e-20260331-arm64'
Line 61 in d0ff8da
Now that we publish to Test PyPI on every commit, we need a new version for each commit. Otherwise, publishing will fail every time, and we won't be told if the publishing pipeline is working or not.
This also means that Rally needs to be "installed" to be used, as this is when the version file is created. The developing Rally instructions don't need to change, as this is the default behavior of uv sync.