Hello Bitbucket Team,
I am facing challenges with managing pipeline executions triggered by PRs across different repositories. I have two main concerns:
atlassian/trigger-pipeline
pipe) also cancels the dependent pipeline in the other repository?I need a way to link these pipeline lifecycles to improve efficiency and resource management. Is there a feature or method within Bitbucket that supports these requirements, or are there plans to introduce such functionality?
Thank you for your assistance.
Hello @Adi Sasson ,
and welcome to the Community!
Bitbucket Pipelines does not natively support automatically canceling a running pipeline when a new commit triggers another pipeline for the same PR. I went ahead and created a feature request for this scenario:
As for canceling dependent pipelines that were triggered with atlassian/trigger-pipeline, Bitbucket does not automatically link the lifecycle of these pipelines, as such, canceling the initiating pipeline does not cancel the triggered pipeline. I've also raised a feature for this request :
I would suggest you to add your vote in those features, since this helps both developers and product managers to understand the interest. Also, make sure you add yourself as a watcher in case you want to receive first-hand updates from that ticket. Please note that all features are implemented with this policy in mind.
Thank you, @Adi Sasson !
Patrik S
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.