Actions
action #175305
closedcoordination #154768: [saga][epic][ux] State-of-art user experience for openQA
coordination #157345: [epic] Improved test reviewer user experience
Flag to return restarted jobs when using openQA jobs API route size:S
Start date:
2024-12-19
Due date:
% Done:
0%
Estimated time:
Tags:
Description
Observation¶
When jobs are restarted the according original job no longer reflects the state of the new job. It would be helpful to provide the new job via the jobs API.
See #174583 for the original context.
Acceptance Criteria¶
- AC1: openQA provides an API to find restarted jobs from the original ones
- AC2: By default jobs are returned regardless of restarts
- AC3: openqa-cli monitor can "follow" restarts via this new feature
Suggestions¶
- Add a parameter to the jobs API (e.g.
follow=1) - Add the flag to routes where it makes sense, add it especially to the route the openqa-cli monitor command is using
- The web UI already links restarted jobs - this is about the API, but maybe code can be shared
Updated by livdywan 16 days ago
- Copied from action #174583: openqa/scripts-ci pipeline fails, jobs ended up in various not-ok states - New openQA API route to follow job obsolescence? size:S added
Updated by openqa_review 13 days ago
- Due date set to 2025-01-31
Setting due date based on mean cycle time of SUSE QE Tools
Actions