Allow to populate just jobs/marks/tags
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 Evgeny Novikov about 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.