Project

General

Profile

Feature #8436

Feature #8434: Get rid of job classes

Switch to configuration driven results processing

Added by Evgeny Novikov over 1 year ago. Updated 3 months ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Results processing
Target version:
Start date:
09/18/2017
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

A long ago I assumed that we will have a lot of job classes for various types of target programs, and for each such class it will be necessary to invoke specific results processing components of Core. Now I think that it would be better to do that in accordance with specified configuration options since this is a more flexible and generic approach.

History

#1 Updated by Evgeny Novikov about 1 year ago

  • Assignee changed from Evgeny Novikov to Ilja Zakharov

Let's Ilja will do this as well as #8435.

#2 Updated by Evgeny Novikov 8 months ago

  • Target version changed from 2.0 to 1.0

#3 Updated by Evgeny Novikov 8 months ago

  • Target version changed from 1.0 to 2.0

#4 Updated by Ilja Zakharov 4 months ago

  • Status changed from New to Resolved

Implemented long ago in Klever 2.0.

#5 Updated by Evgeny Novikov 3 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