How can I avoid that Pipelines runs for each branch on the same commit?

[rbarriuso]

I've noticed that Pipelines runs automatically every time that a branch is moved (fast-forward) to a more recent commit.

In our way of working, usually developers use dev branches in which Pipelines already runs every time a commit is pushed. Then all dev branches are merged into master and then all dev branches are fast-forwarded to the latest state of master.

In this last step, since Pipelines already run on the most recent commit (pushed to master branch), I think it's redundant that it runs again only because the dev branches are fast-forwarded and pushed to that same commit.

Is this something that can be configured? It would be great to avoid that Pipelines runs on a commit in which it already ran before.

[davina]

Hi Rafael,

Pipelines currently doesn't support this but I suggest you raise a feature request for it at http://bitbucket.org/site/master/issues and choose Pipelines as the component.

Another open feature request is Pipelines configuration for Pull requests that you might also be interested in.

Hope this helps!

[rbarriuso]

Done: https://bitbucket.org/site/master/issues/16119/configuration-to-avoid-running-several

Thanks!