Project

General

Profile

Actions

action #111770

closed

coordination #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

Added by okurz almost 2 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2022-05-30
Due date:
% Done:

0%

Estimated time:

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

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

Related issues 1 (0 open1 closed)

Copied to openQA Project - action #114421: Add a limit where it makes sense after we have it for /tests, query configurable size:MResolvedrobert.richardson

Actions
Actions #1

Updated by okurz over 1 year ago

  • Target version changed from Ready to future
Actions #2

Updated by okurz over 1 year ago

  • Subject changed from Limit all displayed tests on /tests, but query configurable and show complete number of jobs to Limit finished tests on /tests, but query configurable and show complete number of jobs size:S
  • Description updated (diff)
  • Status changed from New to Workable
  • Target version changed from future to Ready
Actions #3

Updated by okurz over 1 year ago

  • Copied to action #114421: Add a limit where it makes sense after we have it for /tests, query configurable size:M added
Actions #4

Updated by mkittler over 1 year ago

  • Assignee set to mkittler
Actions #5

Updated by mkittler over 1 year ago

  • Status changed from Workable to In Progress
Actions #6

Updated by mkittler over 1 year ago

  • Status changed from In Progress to Feedback

The PR has been merged

Actions #7

Updated by kraih over 1 year ago

Is there an indicator telling the user that the number of results has been limited? With a new limited that's configured on the server side, it could be surprising to the user otherwise.

Actions #8

Updated by mkittler over 1 year ago

  • Status changed from Feedback to Resolved

It says "Last X jobs" anyways. That a limit specified via a query parameter is clamped should therefore be apparent (and hopefully also not surprise anyone).

The change has been deployed on OSD and it works. Both ACs are fulfilled so I'm setting the ticket to resolved.

Actions #9

Updated by okurz over 1 year ago

  • Status changed from Resolved to Feedback

The feature works as expected, e.g. https://openqa.opensuse.org/tests?limit=100000&match=krypton-live goes back 4 years. But I couldn't find any hint on the webUI how users would be able to do this, see the suggestion "Add help text on the web UI (or documentation); Optional: UI elements to configure the limit directly"

Actions #11

Updated by mkittler over 1 year ago

  • Status changed from Feedback to Resolved

The PR has been merged.

Actions

Also available in: Atom PDF