Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-12146

Branch merging with gatekeeper and push on causes git failures with concurrent builds

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Plan Branches
    • 0
    • 2

    • 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

      If I have a repository setup on the gatekeeper, with multiple branches, committing to two branches at nearly the same time will trigger both branches to build. One branch will finish before the other, and therefore push the remote HEAD forward. If the second build cannot merge as a fast-forward, it will fail to merge and fail to build. Simply re-running the second build will result in success because it will pull the changes that the first pushed on success. A safer strategy would be to not allow multiple branches to run if they are set to push on success.

      Attachments

        Issue Links

          duplicates

          Suggestion - BAM-11007 Gatekeeper with push requires the commits into that repository to be serialized

          • Gathering Interest
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. BAM-12926 Wrong commits are checked out using Gatekeeper auto-merging

          • Low - Low priority issues
          • Closed

          Activity

            People

              Unassigned Unassigned
              akhachatryan ArmenA
              Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated: