Details
-
Fix
-
Status: Released (View Workflow)
-
Minor
-
Resolution: Fixed
-
1.10
-
None
Description
Current Situation
When having to split nodes in a job chain that have successsors that are following the naming convention splitnode:successor1:successor2 there is no assignemt from splitnode:successor1 to splitnode:successor1:successor2 but from splitnode to splitnode:successor1:successor2
Desired behaviour
The naming convention for split nodes also should cover split nodes in a splitted sub chain.
Example:
<job_chain name="job_chain2"> <job_chain_node state="start" job="job1"/> <job_chain_node state="split" job="split" next_state="sync" error_state="error"/> <job_chain_node state="sync" job="sycn" next_state="success" error_state="error"/> <job_chain_node state="split:10" job="job2" next_state="sync" error_state="error"/> <job_chain_node state="split:20" job="job3" next_state="sync" error_state="error"/> <job_chain_node state="split:30" job="job5" next_state="sync2" error_state="error"/> <job_chain_node state="sync2" job="sync3" next_state="success" error_state="error"/> <job_chain_node state="split:30:100" job="job6" next_state="sync2" error_state="error"/> <job_chain_node state="split:30:200" job="job7" next_state="sync2" error_state="error"/> <job_chain_node state="split:30:300" job="job9" next_state="sync2" error_state="error"/> <job_chain_node state="success"/> <job_chain_node state="error"/> </job_chain>