SovereignCloudStack / SovereignCloudStack/standards
Compliance test report should contain info about test suite version
@mbuechse is already working on this.
Since Sep 6, 2024.
- Dominant language
- Python
- Stars
- 47
- Forks
- 38
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 8
Description
To this end, introduce a double-underscore version variable.
This is particularly relevant for those CSPs that run the tests themselves.
Originally, this proposed to include the commit id, but it might be possible that no "actual" git checkout is used -- as is the case with Zuul (which uses some kind of mock checkout), or with pip (assuming that we make the test suite installable via pip).
Originally, this also speculated that git status could be used to detect any form of hampering, which doesn't work for the same reason. We can compute some kind of hash of the most important files though. I would leave that for a future issue. (YAGNI)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.