Record Testing Farm usage via ATEX using Testing Farm tags
#14337
+14
−3
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.
Description:
This encodes additional metadata using a generic JSON object called
tagsin the Testing Farm API: https://api.testing-farm.io/docs#operation/request_a_new_test_v0_1_requests_postRationale:
With Packit-based Testing Farm usage, we had at least rough idea of who is running the test by git repo URL, ie.
but with ATEX, we only get
because it simply reserves systems from TF, and only then runs tests on them.
This PR adds additional metadata to reserve "requests" (which is what TF calls jobs, basically) to help us at least approximate who is pushing too frequently / using too much of TF resources.
Review Hints:
This might need to be a blind review since I can't change the workflow and test it in the same PR.