Packit API enhancement - make /testing-farm/results parametrizable, expose ref #2221
Open
2 tasks done
Labels
API
Related to the API of the packit-service.
area/general
Related to whole service, not a specific part/integration.
complexity/single-task
Regular task, should be done within days.
gain/high
This brings a lot of value to (not strictly a lot of) users.
impact/low
This issue impacts only a few users.
kind/feature
New feature or a request for enhancement.
Description
Gathering data for test results from the Testing Farm is very time demanding and tedious with growing number of pipelines. One needs to go over each check, click the respective hyperlink and scroll through the results. We have our own way to easily parse the results from the result page/artifact URL, however getting to the pipeline_id and or URL is the pain point.
One way to get to the result page/pipeline ID "faster" is to parse the Packit's API
/testing-farm/results
and/or/projects/{forge}/{namespace}/{repo_name}/prs
namespace.The issue with the
/testing-farm/results
is, that it contains all the projects' testing-farm requests handled by packit with no way to parametrize the query. Being able to parametrize the query to narrow the results to a specific project would speed up the data gathering immensely.The other option, however not exclusive to the testing-farm namespace enhancement is exposing
ref
and possibly any type of timestamp for the/projects/{forge}/{namespace}/{repo_name}/prs
response body. Specifically inside the tests field.Benefit
If proven working, we could provide the artifact URL gathering and reporting functionality to packit itself. This could help to resolve #2205
Additionally, there could be
/packit report
feature provided in the future to report the test results by Packit in a comment.Importance
high
It's not blocking us to use Packit per se, but it's faster to query for results if we use our wrapper to schedule test jobs and parse the resulting request pipeline IDs.
What is the impacted category (job)?
Testing Farm tests
Workaround
Participation
The text was updated successfully, but these errors were encountered: