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

Branches are created/triggered even with Plan disabled

XMLWordPrintable

      Steps to reproduce
      1. create application link between Bamboo v5.7.2 and Stash v3.6.0
      2. create a repository in Stash
      3. commit something to the repository
      4. create a Project / Plan in Bamboo
      5. set up Stash repository in "Plan configuration >> Repositories" tab
      6. under "Plan configuration >> Triggers" tab, select "Stash repository triggers the build when changes are committed" as "Trigger type"
      7. under "Plan configuration >> Branches" tab, enable "Create plan branches for branches detected in the repository"
      8. run your build
      9. disable your build Plan
      10. create a new Branch 
        git checkout -b newbranch
      11. commit something to the "newbranch"

      You will notice a new branch will be displayed under the Plan in Bamboo and the same will trigger a build.

            [BAM-15536] Branches are created/triggered even with Plan disabled

            Eduardo Alvarenga (Inactive) made changes -
            Remote Link Original: This issue links to "BDEV-8801 (Atlassian JIRA Extranet - Special Projects)" [ 101847 ] New: This issue links to "BDEV-8801 (Hello Jira)" [ 101847 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1443787 ] New: JAC Bug Workflow v3 [ 3382515 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1422123 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1443787 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 828852 ] New: Bamboo Workflow 2016 v1 [ 1422123 ]

            Deleted Account (Inactive) added a comment -

            I agree, if a plan is disabled, it should be completely disabled. Current behavior violates principle of least surprise.

            Deleted Account (Inactive) added a comment - I agree, if a plan is disabled, it should be completely disabled. Current behavior violates principle of least surprise.

            Heather Noe added a comment -

            I guess I'm not understanding why this feature is 'wanted'. I would like 1 place to disable the entire plan and it's branches without having to go in and disable each individual branch as well. My plan has a polling trigger setup for all branches, I would like to see that if the plan is disabled, the polling of branches associated w/ that plan is also disabled, that way when I re-enable the plan, all branches automatically start polling again without out further changes required by the user.

            Heather Noe added a comment - I guess I'm not understanding why this feature is 'wanted'. I would like 1 place to disable the entire plan and it's branches without having to go in and disable each individual branch as well. My plan has a polling trigger setup for all branches, I would like to see that if the plan is disabled, the polling of branches associated w/ that plan is also disabled, that way when I re-enable the plan, all branches automatically start polling again without out further changes required by the user.
            Przemek Bruski made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Needs Triage [ 10030 ] New: Resolved [ 5 ]

            Przemek Bruski added a comment -

            This behaviour is intended. You disabled the main branch, so it won't build, but at the same time the branch detection is still enabled.

            Przemek Bruski added a comment - This behaviour is intended. You disabled the main branch, so it won't build, but at the same time the branch detection is still enabled.
            Przemek Bruski made changes -
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]
            Bruno Rosa made changes -
            Affects Version/s New: 5.9.7 [ 58593 ]

              Unassigned Unassigned
              rsperafico Rafael Sperafico (Inactive)
              Affected customers:
              4 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: