• Icon: Bug Bug
    • Resolution: Answered
    • Icon: Low Low
    • None
    • 5.9.7
    • None
    • None

      Steps to reproduce

      1. Go to the Plan Configuration >> Plan details page.
      2. Uncheck the Plan enabled option.

      Expected behavior

      If the Plan has been disabled, all the options under 'Automatically manage branches' should be turned off automatically. As a result, Bamboo will stop trying to poll the primary source repository looking for changes.

      Problem

      If any of the options inside Plan Configuration >> Branches under 'Automatically manage branches' are enabled after disabling a Plan, Bamboo will keep trying to poll the repository.

      Workaround

      Disable all the 3 options under 'Automatically manage branches'.

       

            [BAM-16632] Disabled Plan keeps trying to poll repository

            I have the same issue.  How is the current behavior expected or desirable?

            Why would anyone want a disabled plan to continue branching after it has been disabled?  I can't think of any reason that would be the desired behaviour.

            Phil Rittenhouse added a comment - I have the same issue.  How is the current behavior expected or desirable? Why would anyone want a disabled plan to continue branching after it has been disabled?  I can't think of any reason that would be the desired behaviour.

            Disabling the plan disables that branch only. It does not affect the status of other branches or detection of new branches.

            Przemek Bruski added a comment - Disabling the plan disables that branch only. It does not affect the status of other branches or detection of new branches.

            Not a bug.

            Przemek Bruski added a comment - Not a bug.

            Furthermore continuous polling and failing when Authentication error happens results in the ADS account being locked. We found after a recent GitHub update that user/password method of authentication that used to work before the upgrade is not working after the upgrade, The continuous polling CONTINUES to lock the ADS user account of those people who configured their plans with Github access using their or a group account ADS userid.
            I've had to DELETE their Plans and reconfigure using SSH authentication to get around this somewhat related problem.

            Craig Solinski added a comment - Furthermore continuous polling and failing when Authentication error happens results in the ADS account being locked. We found after a recent GitHub update that user/password method of authentication that used to work before the upgrade is not working after the upgrade, The continuous polling CONTINUES to lock the ADS user account of those people who configured their plans with Github access using their or a group account ADS userid. I've had to DELETE their Plans and reconfigure using SSH authentication to get around this somewhat related problem.

              Unassigned Unassigned
              brosa Bruno Rosa
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: