The new update made it so that every time a new commit is pushed to a branch, instead of a new build starting on that branch, it gets disabled.

      After pressing Scan Multibranch Pipeline Now, everything returns to normal.

      This error came up only after updating the plugin to 737.vdf9dc06105be and went away as soon as I downgraded to 2.9.11.

          [JENKINS-67538] Branches with newly pushed commits get disabled

          We noticed exactly the same issue this morning after also upgrading to BBBS 737.vdf9dc06105be last Friday. 'Scan Multibranch Pipeline Now' would enable the target branch for a build, but the next PR to that branch would disable the branch again. We also fixed by rolling back from 737.vdf9dc06105be to 2.9.11

           

          Warren Humphreys added a comment - We noticed exactly the same issue this morning after also upgrading to BBBS 737.vdf9dc06105be last Friday. 'Scan Multibranch Pipeline Now' would enable the target branch for a build, but the next PR to that branch would disable the branch again. We also fixed by rolling back from 737.vdf9dc06105be to 2.9.11  

          Please update to at least version 746.v350d2781c184

          Günter Grodotzki added a comment - Please update to at least version 746.v350d2781c184

            Unassigned Unassigned
            rolaca11 László Stahorszki
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: