Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-16119

Configuration to avoid running several times on the same commit

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      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.

      It would be nice to be able to configure Pipelines to avoid running on a commit in which it already ran before.

      Attachments

        Activity

          People

            Unassigned Unassigned
            1a61b1830544 rbarriuso
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: