I have a scenario where I use the predeployment to create a bunch of steps (I think the largest deployment had like ~70 steps) and of course I also need to handle the dependencies between those steps.
And here comes my questions, so far I only know of the action
- ROC - Add Step Dependency
where I enter the step name and an array of the preceding steps as parameters.
The problem I'm facing is, that I can't create the steps already in the order they are supposed to be executed, as this would be an absolute nightmare of a flow to implement with the given possibilites in CA RA.
Let's use a small example to visualize my issue:
I now want to create another DeployStepD that should be executed between DeployStepA and DeployStepB, so that in the end my deployment would like this
To achieve this I'm currently doing the following:
Calling the "Add Step Dependency" action once where I define that DeployStepA is a predecessor of DeployStepD and then I do a loop that goes through DeployStepB and DeployStepC to set DeployStepD as their predecessor.
I have the feeling that the loop costs a lot of time, it looks very slow in the UI. Although I'm not sure if it really takes that long in the backend to set up all dependencies or if the visiualization in the UI is the bottleneck here.
Anyway if the loop would be the issue, is there a way to fasten this up or would it be more the opener for an idea to have a second "Add Step Dependency" action, but where you could define the steps that should be executed after the given step?
That being said, looking forward to a discussion about this question. Maybe someone from CA has more details about this stuff and could even tell me, if really the UI might be a factor here as well that slows down this dependency handling, as in the UI steps get moved around the list and dependency numbers are being changed and added too.