Actions
action #111770
closedcoordination #80142: [saga][epic] Scale out: Redundant/load-balancing deployments of openQA, easy containers, containers on kubernetes
coordination #92854: [epic] limit overload of openQA webUI by heavy requests
action #97190: Limit size of initial requests everywhere, e.g. /, /tests, etc., over webUI and API
Limit finished tests on /tests, but query configurable and show complete number of jobs size:S
Description
Acceptance criteria¶
- AC1: The number of finished tests on /tests is configurable by the user (with query parameter
limit), but limited server-side - AC2: By default we still show up to 500 finished jobs
Suggestions¶
- Look into what we recently did for the /tests/overview page where we also added an alert box if results are limited to 500, https://github.com/os-autoinst/openQA/blob/master/lib/OpenQA/WebAPI/Controller/Test.pm#L55
- Ensure there is a query parameter available to users to configure the number of results
- Ensure there is a server-side limit
- Add help text on the web UI (or documentation)
- Optional: UI elements to configure the limit directly
Out of scope¶
- Anything regarding direct use of the API, this is only about web UI
- This is only about "finished" tests. "scheduled" and "running" to be handled in parent epic
Actions