Project

General

Profile

Feature #9128

Distinguish production and non-production preset jobs and marks

Added by Evgeny Novikov 11 months ago. Updated 9 months ago.

Status:
Closed
Priority:
Urgent
Category:
Bridge
Target version:
Start date:
07/18/2018
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

At the moment during population all preset jobs and marks are uploaded. For development and testing purposes that is well, but for the production use case users get several redundant jobs and hundreds of redundant marks intended for those jobs. This not only confuses production users but also can cause quite considerable overhead for many operations.

I suggest to have a dedicated setting, e.g. _POPULATE_JUST_PRODUCTION_PRESETS _ that can be either true or false. By default it should be true for the production mode and false for the development one. Because of testing needs the production mode with non-production preset jobs and marks, we can not use the mode as this setting.

Besides, production preset jobs and marks should be explicitly marked, e.g. with Boolean flag production within main preset files, and Bridge should distinguish them appropriately.


Related issues

Blocks Klever - Feature #9129: Specify production preset jobs and marksClosed07/18/2018

Actions

History

#1

Updated by Evgeny Novikov 11 months ago

  • Blocks Feature #9129: Specify production preset jobs and marks added
#2

Updated by Evgeny Novikov 11 months ago

  • Subject changed from Distinguish production and non-production preset jobs abd marks to Distinguish production and non-production preset jobs and marks
#3

Updated by Vladimir Gratinskiy 9 months ago

  • Status changed from New to Resolved

Implemented in bridge-2.0. All presets marked as for production.

#4

Updated by Evgeny Novikov 9 months ago

  • Status changed from Resolved to Closed

Tests passed, so, I merged the branch to master in b8bda00ac.

Also available in: Atom PDF