You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently attempted to use the codefresh-dynamic-run step for a release process that involves a variable number of environments (I realize it is incubating). My plan was to generate the dynamic-run yaml based on existing configuration and spawn N child pipelines to carry out the release process. Technically the step works, I was able to pass the required parameters to a generalized child pipeline, however the visual feedback makes the step very confusing for a broad user base. I have resorted to a more static approach to my process in order to preserve the visual feedback users will expect without searching through logs to determine a dependent pipeline.
I would request that:
-a node is created in the graph for each sub pipeline in the dynamic run step
-the node has a link to the child pipeline execution
-the node indicates the status of the child pipeline execution
I am guessing this may already be under consideration, but I just wanted to reiterate the importance of the dynamic-run step for more complex pipeline design and value of visual feedback for end users.
The text was updated successfully, but these errors were encountered:
I recently attempted to use the codefresh-dynamic-run step for a release process that involves a variable number of environments (I realize it is incubating). My plan was to generate the dynamic-run yaml based on existing configuration and spawn N child pipelines to carry out the release process. Technically the step works, I was able to pass the required parameters to a generalized child pipeline, however the visual feedback makes the step very confusing for a broad user base. I have resorted to a more static approach to my process in order to preserve the visual feedback users will expect without searching through logs to determine a dependent pipeline.
I would request that:
-a node is created in the graph for each sub pipeline in the dynamic run step
-the node has a link to the child pipeline execution
-the node indicates the status of the child pipeline execution
I am guessing this may already be under consideration, but I just wanted to reiterate the importance of the dynamic-run step for more complex pipeline design and value of visual feedback for end users.
The text was updated successfully, but these errors were encountered: