chain multiple API triggered workflows together so that they behave as a single pipeline and not as N independent workflows
J
Joran Fonjallaz
We have a monorepo, and some complex workflows. It would be great to be able to use circleci API calls to trigger workflows within the same project, as this is an elegant way to pass parameters around, and to decouple different jobs.In the example provided, pushing commits to the repo triggered the workflow foo, which triggered by API call the workflow bar. However, from circleci's point of view those two workflows (foo and bar) are completely decoupled.they have different ID in the UIeven though bar failed, foo succeededI believe it could be every useful to be able to pass a UUID in API calls triggering a pipeline, so that all workflows with the same UUID behave as a single one.
CCI-I-1583