Actions
Feature #8434
closedGet rid of job classes
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:
- 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.
- Specific Core components for solving them. This should be replaced with using universal components and their specific configurations.
- 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.
- Specific Bridge components for visualizing their verification results. Here we suppose to switch to also a more flexible approach of specific data visualization.
Actions