Feature #8989
closedAllow to populate just jobs/marks/tags
Added by Evgeny Novikov over 6 years ago. Updated almost 5 years ago.
100%
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.
Updated by Vladimir Gratinskiy over 6 years ago
Population is not a developer feature. It's needed for deployment only.
Updated by Evgeny Novikov over 6 years 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.
Updated by Evgeny Novikov over 6 years ago
- Target version deleted (
1.0)
This was marked for 1.0 by mistake.
Updated by Vladimir Gratinskiy over 5 years ago
- Due date set to 07/11/2019
- Status changed from New to Resolved
- % Done changed from 0 to 100
Implemented in bridge-3.0 (population is on manager page now).
Updated by Evgeny Novikov about 5 years 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.
Updated by Evgeny Novikov about 5 years 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.
Updated by Vladimir Gratinskiy about 5 years ago
- Blocked by Feature #9858: Support new verification jobs base added
Updated by Evgeny Novikov about 5 years 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.