Trigger pipelines from other pipelines
L
Luis Pabon
This allows for more complex orchestration of workflows that span multiple repositories, common for instance when you're building & deploying microservices with inter-dependencies. Currently we need to code our own solution to trigger the next pipeline, watch it, handle error completions and timeouts. There's also no visual feedback either of course and Github checks integrations also needs to be coded in.
Daniël Schenk
Apart from needing additional code to monitor the triggered pipeline if we would want the triggering pipeline to reflect its status, there's also the downside that a personal API token is required for this, which is fixed as an env var in the project. This means that any failure in the triggered pipeline would be notified to the owner of that token, and not to the person who authored the commit which triggered the failure.
S
Salverda Jorrit
The current approach with making direct API requests indeed doesn't feel very 'native', so a real cross-project trigger is desirable.
Linking pipelines is a pretty basic feature of many CI/CD systems, see following docs: