Project

General

Profile

Feature #8434

Get rid of job classes

Added by Evgeny Novikov about 2 years ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
09/18/2017
Due date:
12/14/2017
% Done:

100%

Estimated time:
(Total: 0.00 h)
Published in build:

Description

A long ago I assumed that we will have a lot of job classes for various types of target programs. These classes can't be intermixed. For each job class there can be:
  1. Specific means for setting corresponding jobs in Bridge. Indeed this won't be ever implemented since it is too hard. The only universal format is providing a number of specification and configuration files.
  2. Specific Core components for solving them. This should be replaced with using universal components and their specific configurations.
  3. Specific Core components for reporting their verification results. For this we suppose to use a more flexible approach by configuring verification results processing like other steps of the static verification workflow.
  4. Specific Bridge components for visualizing their verification results. Here we suppose to switch to also a more flexible approach of specific data visualization.

Subtasks

Feature #8435: Always start up the same Core componentsClosedIlja Zakharov

Actions
Feature #8436: Switch to configuration driven results processingClosedIlja Zakharov

Actions
Feature #8437: Get rid of job classesClosedVladimir Gratinskiy

Actions

Related issues

Related to Klever - Feature #8889: Support verification job formats properlyNew05/24/2018

Actions
Related to Klever - Feature #9313: Introduce top level configuration options for processing verification resultsNew10/08/2018

Actions

History

#1

Updated by Evgeny Novikov about 2 years ago

  • Description updated (diff)
#2

Updated by Evgeny Novikov over 1 year ago

  • Target version changed from 2.0 to 1.0

We have to implement this issue, since Bridge won't support job classes in Klever 1.0.

#3

Updated by Evgeny Novikov over 1 year ago

  • Target version changed from 1.0 to 2.0

I implemented a workaround in branch core-new-formats since a proper solution is complicated. So, now one should specify attribute Class explicitly within job.json. You can find examples in preset jobs. If you will try to solve old jobs with a new version of Klever, you will need to update them appropriately.

#4

Updated by Evgeny Novikov over 1 year ago

  • Related to Feature #8889: Support verification job formats properly added
#5

Updated by Evgeny Novikov about 1 year ago

  • Status changed from New to Resolved

All was done. The only thing I dislike is results processing. At the moment there is not a straightforward configuration options both in jobs and reports that control this. Instead both Core and Bridge reveal various job types on the basis of some rather low level data. Let's proceed one day later.

#6

Updated by Evgeny Novikov about 1 year ago

  • Related to Feature #9313: Introduce top level configuration options for processing verification results added
#7

Updated by Evgeny Novikov 12 months ago

  • Status changed from Resolved to Closed

Branch klever-2.0 passed all tests and I merged it to master in 72be796e3 marked as v2.0rc1.

Also available in: Atom PDF