Actions
action #11052
closedExtensions on build and job tagging
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2015-11-14
Due date:
% Done:
0%
Estimated time:
Description
user stories¶
- As a developer working on bugs I want to have access to the original jobs used for reporting to better understand the original issue of a bug
- DONE: As a QA SLE product manager I want to be able to easily find results from older important builds to review for documentation reasons like I am used to with testopia
- As a user of assets on an openQA server I want these assets to stay around for longer for tagged builds to prevent the asset getting lost while I am still relying on it, e.g. for bug investigation
acceptance criteria¶
- jobs "tagged" are kept around longer than non-tagged jobs
- DONE: a UI-only way exists to show only important builds but also including ones that are older than 14 days -> gh#807
- assets, e.g. isos, of tagged builds are not cleaned as agressively as untagged builds
tasks¶
- TODO
Updated by okurz about 8 years ago
- Copied from action #9544: Build Tagging added
Updated by okurz about 8 years ago
- Copied from deleted (action #9544: Build Tagging)
Updated by coolo over 6 years ago
- Status changed from New to Resolved
this is a somewhere between resolved and rejected. Tagged jobs are kept longer, but we can't afford to keep assets longer and as such I don't want to have this implemented. Milestones have to be kept somewhere else. openqa is not an ISO archive.
Actions