new GenericBuildPipelineWorker(args)
Parameters:
| Name |
Type |
Description |
args |
GenericBuildPipelineWorkerConstructorArgs.<BUILD_ARGS, STATES, DFA_GROUPS, PSEUDO_STATES>
|
|
- Source:
Members
pseudoStates :GenericBuildPipelineWorkerPseudoStates.<PSEUDO_STATES>
Type:
-
GenericBuildPipelineWorkerPseudoStates.<PSEUDO_STATES>
- Source:
stateTransitionDefinition :BuildPipelineStatesDFA.<BUILD_ARGS, STATES, DFA_GROUPS>
Type:
-
BuildPipelineStatesDFA.<BUILD_ARGS, STATES, DFA_GROUPS>
- Source:
Methods
isBuildValid(args)
Confirms if a build is valid, or a transition request is. Must have same stamp, and state in args same as self
Latter help with new problem regarding data manager view manager continue callback calls
IN CASE ANYTHING BREAKS, CHECK HERE
Parameters:
| Name |
Type |
Description |
args |
GenericBuildPipelineBuildArgs.<BUILD_ARGS, STATES, DFA_GROUPS>
|
|
- Source:
startPipelineBuild(args)
transition consents to move to next or fail.
/**
Parameters:
| Name |
Type |
Description |
args |
GenericBuildPipelineBuildArgs.<BUILD_ARGS, STATES, DFA_GROUPS>
|
Override To add anything to args or define the targetDFAKey.
MUST Call super to trigger state transition correctly, with checks on pipeline lock |
- Source:
transitionPipelineState(args)
DON'T OVERRIDE. Internal
Trigger the next state transition
HOW THIS ALGO WORKS
We need DFA GROUP and DFA SOURCED (used in cb resolution)
Idea is, next state in DFA group. Thus, send nextTransitionKey in transitionDFAInfo
If nextTransitionKey not in current group, then search if it represents a new DFA group, then flow from root
IMPLEMENT SUPER PIPELINE LOCK. DENY CB IF IN SUCH STATE
Parameters:
| Name |
Type |
Description |
args |
GenericBuildPipelineBuildArgs.<BUILD_ARGS, STATES, DFA_GROUPS>
|
|
- Source: