Im wondering. we have pipeline with different stages. I want another pipeline, my e2e tests, to be triggered after tests stage has been deployed. How to configure that ?
Thanks for the video. It assures me that I have my inter-pipeline triggering (resources) setup correctly.
However when I tried to ALSO trigger my "downstream" pipeline from a local commit on that same pipeline, then that action somehow corrupted my "upstream" pipeline in another project! Microsoft support has recently just fixed the problem in the "upstream" pipeline and it's back (was not showing the Runs, some SQL issue?)
My question that I am struggling with (that I have found ZERO documentation on) is how to have a "downstream" pipeline get triggered by multiple trigger sources: (1) "upstream" pipeline (in a different project) OR (2) local commit on the "downstream" pipeline. – I am curious if you know the answer to that or have tried testing something like this previously. Thanks for posting the video. Cheers,
Thank you very much for the video, how I can do the same but with release pipelines?? I would like to run a release pipeline and then run another release pipeline
Thanks have read about templates but now I see, they are like task groups in DevOps server 2019 right? You just can call them. Can you pass variables too?
Thanks a lot Houssem, your example was way more concrete than the Azure documentation !
But how do you call another Pipeline in another repo? error: /….yml: File /… not found in repository
Im wondering. we have pipeline with different stages. I want another pipeline, my e2e tests, to be triggered after tests stage has been deployed. How to configure that ?
Thanks for the video. It assures me that I have my inter-pipeline triggering (resources) setup correctly.
However when I tried to ALSO trigger my "downstream" pipeline from a local commit on that same pipeline, then that action somehow corrupted my "upstream" pipeline in another project! Microsoft support has recently just fixed the problem in the "upstream" pipeline and it's back (was not showing the Runs, some SQL issue?)
My question that I am struggling with (that I have found ZERO documentation on) is how to have a "downstream" pipeline get triggered by multiple trigger sources: (1) "upstream" pipeline (in a different project)
OR
(2) local commit on the "downstream" pipeline.
–
I am curious if you know the answer to that or have tried testing something like this previously. Thanks for posting the video.
Cheers,
Thank you very much for the video, how I can do the same but with release pipelines?? I would like to run a release pipeline and then run another release pipeline
Useful video, thanks Houssem!
Very usefull content so far, Could you please create more video on this with real life scenario ?
Thanks!
Thanks for sharing Houssem š the code in the repo is really simple to understand. Thank you very much!
how can we trigger a release pipeline from another release pipeline?
Thanks have read about templates but now I see, they are like task groups in DevOps server 2019 right? You just can call them. Can you pass variables too?