Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tmt should log and expose git refs it clones #3444

Open
happz opened this issue Jan 5, 2025 · 0 comments
Open

tmt should log and expose git refs it clones #3444

happz opened this issue Jan 5, 2025 · 0 comments
Labels
area | results Related to how tmt stores and shares results

Comments

@happz
Copy link
Collaborator

happz commented Jan 5, 2025

In its simplest workflow, tmt is executed in a directory with tests, plans, and stories. That's fine. Then the test becomes a git repository, with a history of changes, and then tests become more complicated and start using beaker libraries, and then plans start referencing remote plans from other git repositories, and so on. Users interested in reproducible testing may (and do) ask a question of what plans and tests - exactly, please - were used in a given test run, and tmt should be more helpful by logging and exposing refs of various repositories it encounters.

The implementation may as simple as extending tmt.utils.git_clone() by adding git rev-parse HEAD & logging the output. It might be good enough to start with, but eventually, tmt could provide this info in a more structured way, e.g. via a dedicated YAML file.

Related to https://issues.redhat.com/browse/TFT-3050

@happz happz added the area | results Related to how tmt stores and shares results label Jan 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area | results Related to how tmt stores and shares results
Projects
None yet
Development

No branches or pull requests

1 participant