Project

General

Profile

Feature #8989

Allow to populate just jobs/marks/tags

Added by Evgeny Novikov over 1 year ago. Updated 27 days ago.

Status:
Resolved
Priority:
High
Category:
Bridge
Target version:
Start date:
06/22/2018
Due date:
07/11/2019
% Done:

100%

Estimated time:
Published in build:

Description

At the moment Bridge populates all preset entities although sometimes, e.g. when developing preset marks, it isn't necessary to populate jobs more and more times.


Related issues

Blocked by Klever - Feature #9858: Support new verification jobs baseResolved10/10/2019

Actions

History

#1

Updated by Vladimir Gratinskiy over 1 year ago

Population is not a developer feature. It's needed for deployment only.

#2

Updated by Evgeny Novikov over 1 year ago

Vladimir Gratinskiy wrote:

Population is not a developer feature. It's needed for deployment only.

First of all developers also make deployment (not only initial installation, but also updates). Besides, even for production deployment it can be very valuable to restrict population. Otherwise there can be many similar (the same) jobs, although one doesn't need them.

BTW, for marks and tags updates are purely incremental, so, nobody complains. Thus, perhaps instead of implementing a switch for enabling/disabling population of verification jobs, we can support incremental population for them as well. I.e. Bridge will compare all files for verification jobs with the same names and populate just new ones or ones where files differ.

#3

Updated by Evgeny Novikov over 1 year ago

  • Target version deleted (1.0)

This was marked for 1.0 by mistake.

#4

Updated by Vladimir Gratinskiy 5 months ago

  • % Done changed from 0 to 100
  • Status changed from New to Resolved
  • Due date set to 07/11/2019

Implemented in bridge-3.0 (population is on manager page now).

#5

Updated by Evgeny Novikov 5 months ago

  • Target version set to 3.0
#6

Updated by Evgeny Novikov 3 months ago

  • Status changed from Resolved to Open

I suggest a small extension. Let's allow to select either all jobs or just some ones (Bridge should get a list of existing ones in advance). For web UI this will be very nice. For CLI Bridge can allow to populate a single job according to specified name.

#7

Updated by Evgeny Novikov 3 months ago

Evgeny Novikov wrote:

Vladimir Gratinskiy wrote:

Population is not a developer feature. It's needed for deployment only.

First of all developers also make deployment (not only initial installation, but also updates). Besides, even for production deployment it can be very valuable to restrict population. Otherwise there can be many similar (the same) jobs, although one doesn't need them.

BTW, for marks and tags updates are purely incremental, so, nobody complains. Thus, perhaps instead of implementing a switch for enabling/disabling population of verification jobs, we can support incremental population for them as well. I.e. Bridge will compare all files for verification jobs with the same names and populate just new ones or ones where files differ.

Rather than to implement the small extension I suggested earlier, it will be much better to implement incremental job population that I suggested a long ago but that was not implemented.

Evgeny Novikov wrote:

I suggest a small extension. Let's allow to select either all jobs or just some ones (Bridge should get a list of existing ones in advance). For web UI this will be very nice. For CLI Bridge can allow to populate a single job according to specified name.

#8

Updated by Vladimir Gratinskiy about 1 month ago

  • Blocked by Feature #9858: Support new verification jobs base added
#9

Updated by Evgeny Novikov 27 days ago

  • Status changed from Open to Resolved

There is a great solution of this issue in klever-3.0. There is no more preset jobs population at all. Instead, users need to either create verification jobs on the base of actual preset ones or copy previously created verification jobs.

Also available in: Atom PDF