Actions
Feature #8436
closedFeature #8434: Get rid of job classes
Switch to configuration driven results processing
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.
Actions