Feature #8337
closed
Upload reports without job decision
Added by Pavel Andrianov over 6 years ago.
Updated over 6 years ago.
Description
The case is when user wants to upload its results without job decision, for example, to visualize an error trace. That is what is partially done in fake_decision branch. The suggestion is to implement it not as manager tool, but for general user as a one more button. Likely, the button should be on the Job page. I am not sure why one can want to upload safe or unknown reports, but in general case the uploaded report may be any type. For example, to visualize coverage.
A question is the format of description of the archive. In fake_decision branch we use simplified format, when attributes like verifier, rule and so on are set to default values.
- Assignee set to Vladimir Gratinskiy
- Priority changed from Normal to Urgent
It has sense to complete useful functionality before implementation of a new one.
Pavel Andrianov wrote:
The suggestion is to implement it not as manager tool, but for general user as a one more button.
By the general user it is assumed users that have rights to solve a given job.
- Status changed from New to Feedback
I added minor notes, let's wait for Pavel's feedback.
Already implemented in branch "feature_8337".
Vladimir Gratinskiy wrote:
Already implemented in branch "feature_8337".
Is this a proper implementation of things started in branch fake-decision? If so, the latter should be deleted after this branch will be merged to master.
Evgeny Novikov wrote:
Vladimir Gratinskiy wrote:
Already implemented in branch "feature_8337".
Is this a proper implementation of things started in branch fake-decision? If so, the latter should be deleted after this branch will be merged to master.
Yes, I think fake-decision can be deleted if nobody need it.
A couple of questions to the document are added, though the format is rather clear, so, I was able to understand it.
- Status changed from Feedback to Open
- Status changed from Open to Resolved
- Target version set to 0.2
- Status changed from Resolved to Open
Please, merge the latest master within this branch - there is a nontrivial conflict.
- Status changed from Open to Resolved
- Status changed from Resolved to Closed
So, I merged the branch to master in 62ef843b and removed branch fake-decision. Don't forget to migrate your databases to allow the feature. Pavel can/should use the modern interface.
Also available in: Atom
PDF