Some people, especially developers who are not using Beaker regularly, are not aware the jobs are completely wiped after some period. /me had just heard one venting his frustration. It is perfectly OK to wipe results and files. But preserve the job definitions, please. Or at least have a warning on the job submit page.
Dear Marian, thanks for the report. With the implementation of the new job page design there is potential for creating a new (readonly-) view providing information of the old job and add the ability to clone it. Unfortunately the bkr client lets you fetch the job XML for a deleted job for cloning but it is somewhat inconsistent with the web UI.
(In reply to Roman Joost from comment #1) > Dear Marian, > > thanks for the report. With the implementation of the new job page design > there is potential for creating a new (readonly-) view providing information > of the old job and add the ability to clone it. > > Unfortunately the bkr client lets you fetch the job XML for a deleted job > for cloning but it is somewhat inconsistent with the web UI. This has already been implemented on the new job page. The deleted jobs can be viewed and cloned, including the recipe sets.
(In reply to matt jia from comment #2) Right, but currently the new job page gives no indication that you are looking at a deleted recipe (and hence it is missing all its results). For this bug we should probably improve the new job page and new recipe page to make it clear if you are looking at a deleted job -- for example, an alert-error at the top saying so. Or something like that but nicer. It should show all the tasks, settings, etc... but it shouldn't offer to show you any results, because there will be none. So people can still see what was in the job as it was originally submitted, and clone it as well.
May be worth tackling bug 1322700 at the same time, although there is nothing tying them together.
I have come out a UI for deleted jobs/recipes: https://gerrit.beaker-project.org/#/c/4804/
Beaker 23.0 has been released.