Details
-
Feature
-
Status: Released (View Workflow)
-
Major
-
Resolution: Fixed
-
1.13
-
None
-
None
Description
Current Situation
- Events are available for use with In Conditions and Out Conditions on a per Master basis
Desired Behavior
- Events should in addition be available across a number of JobScheduler Masters.
- Each Master runs an instance of the Job Streams Plugin. The Plugin instances share the same Reporting Database and make events persistent across Master instances.
- Events can be created at a global level by any Out Condition. Such events are prefixed with "global:". Implicitly events within the scope of an individual Master instance use the scope "local:".
- Global events can be consumed by In Conditions. Such events are referenced by use of the "global:" Prefix.
- The global event x and the local event x are two different events. Therefore, when deleting the event global:event any local events x will not be removed.