action #5428: import results.json into database as much as possible - openQA Project - openSUSE Project Management Tool

Actions

Copy link

action #5428

closed

import results.json into database as much as possible

Added by coolo over 9 years ago. Updated about 9 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

coolo

Category:

Feature requests

Target version:

Sprint 15

Start date:

2015-02-24

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Subtasks 1 (0 open — 1 closed)

Actions

Copy link

Updated by coolo over 9 years ago

working on it in https://github.com/os-autoinst/openQA/tree/issue_5428

Actions

Copy link

Updated by coolo over 9 years ago

Assignee deleted (~~coolo~~)

JobModules now has some of these informations. What's missing

backend information for the job
dents for the modules and dents for the job
flags for the modules

Actions

Copy link

Updated by coolo over 9 years ago

Assignee set to coolo
Target version set to Sprint 13

Actions

Copy link

Updated by coolo over 9 years ago

the dents are in and the flags are. What's left missing:

state of the modules (done, running, todo)
backend infos

Actions

Copy link

Updated by coolo about 9 years ago

Target version deleted (~~Sprint 13~~)

there are only job modules when the job is done, which makes the whole Running controller pretty helpless.

I need the worker to split result.json and submit the interesting parts

Actions

Copy link

Updated by coolo about 9 years ago

the current state:

worker sends all of results.json (interim solution)
the currently running step has 'running' as result

The worker needs be smarter and only send changed modules. And we need a solution for backend infos. E.g. the interactive command is sent to the worker, which translates it in a file for os-autoinst, which then sets a flag in results.json - that is read by the Running controller.

Actions

Copy link