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

Branches still added when plan is disabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None
    • 5.9.1
    • Bitbucket Server integration
    • None

      Problem:

      Plan branches are added for disabled plans

      Steps to Reproduce:

      1. Configure Bamboo to use a linked repository to Stash
      2. In Stash, pull requests to require 1 approver and 1 successful build
      3. Create a build plan in which the option "Automatically manage branches" is checked
      4. Clone this build plan
      5. Disable the cloned build plan.
      6. Make a commit on a new branch

      Both build plans get branch plans created for them, even the disabled on. The build on the disabled plan fails. Stash then sees both a passing build in the original plan and a failed build in the disabled cloned plan. Now Stash will not let the merge go process as it sees the failed build in the disabled plan as not meeting the requirement to allow the pull request to be merged as Stash seems to require a passing build in all plans where the branch build might occur.

      Expected Behavior:

      The desired behavior is that if the overall plan is disabled, it should not allow automatic branch plans to obtain the branch unless manually added.

      Workaround:

      Disable all the individual branch plans or delete the disabled plan.

            [BAM-16094] Branches still added when plan is disabled

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1442983 ] New: JAC Bug Workflow v3 [ 3381037 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1420725 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1442983 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 904246 ] New: Bamboo Workflow 2016 v1 [ 1420725 ]
            Przemek Bruski made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Resolved [ 5 ]
            Przemek Bruski made changes -
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]
            WestonM made changes -
            Link New: This issue is related to BAM-12833 [ BAM-12833 ]
            WestonM made changes -
            Link New: This issue is related to BAM-15536 [ BAM-15536 ]
            WestonM made changes -
            Link New: This issue is related to BAM-13084 [ BAM-13084 ]
            James Giles IV (Inactive) made changes -
            Description Original: h4. Problem:
            Plan branches are added for disabled plans

            h4. Steps to Reproduce:
            # Configure Bamboo to use a linked repository to Stash
            # In Stash, pull requests to require 1 approver and 1 successful build
            # Create a build plan in which the option "Automatically manage branches" is checked
            # Clone this build plan
            # Disable the newly created build plan (not the clone).
            # Make a commit on a new branch

            Both build plans get branch plans created for them, even the disabled on. The build on the disabled plan fails. Stash then sees both a passing build in the original plan and a failed build in the disabled cloned plan. Now Stash will not let the merge go process as it sees the failed build in the disabled plan as not meeting the requirement to allow the pull request to be merged as Stash seems to require a passing build in all plans where the branch build might occur.

            h4. Expected Behavior:
            The desired behavior is that if the overall plan is disabled, it should not allow automatic branch plans to obtain the branch unless manually added.

            h4. Workaround:
            Disable all the individual branch plans or delete the disabled plan.             		New: h4. Problem:
            Plan branches are added for disabled plans

            h4. Steps to Reproduce:
            # Configure Bamboo to use a linked repository to Stash
            # In Stash, pull requests to require 1 approver and 1 successful build
            # Create a build plan in which the option "Automatically manage branches" is checked
            # Clone this build plan
            # Disable the cloned build plan.
            # Make a commit on a new branch

            Both build plans get branch plans created for them, even the disabled on. The build on the disabled plan fails. Stash then sees both a passing build in the original plan and a failed build in the disabled cloned plan. Now Stash will not let the merge go process as it sees the failed build in the disabled plan as not meeting the requirement to allow the pull request to be merged as Stash seems to require a passing build in all plans where the branch build might occur.

            h4. Expected Behavior:
            The desired behavior is that if the overall plan is disabled, it should not allow automatic branch plans to obtain the branch unless manually added.

            h4. Workaround:
            Disable all the individual branch plans or delete the disabled plan.
            Daniel (Inactive) made changes -
            Component/s New: Stash integration [ 18508 ]
            Status Original: Needs Triage [ 10030 ] New: Open [ 1 ]
            James Giles IV (Inactive) created issue -

              Unassigned Unassigned
              jgiles@atlassian.com James Giles IV (Inactive)
              Affected customers:
              2 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: