Introduce batch processing capabilities for the Pipeline Test Reports API
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
Implement batch processing capabilities for the GET /projects/:id/pipelines/:pipeline_id/test_report API endpoint by adding optional query parameters to allow control over the scope of the results returned.
This enhancement allows API consumers to request test reports in configurable smaller batches, similar to the approach used by the web UI. Via the web UI is possible to retrieve all test reports via the UI as it leverages a lazy load approach to prioritize user experience and allows limiting by job_name - /-/pipelines/:pipeline_id//test_report?job_name=job_name
Problem to solve
Currently, the GET /projects/:id/pipelines/:pipeline_id/test_report API endpoint loads complete test report data in a single request.
This results in a PUMA rack timeout where there are a large number of tests.
The customer is reluctant to increase the default Puma timeout as this impacts all requests.