Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-67502

cloudbees-bitbucket-branch-source latest version marks master branch as deleted

      After updating to the latest version Bitbucket push event does not trigger build and `master` branch appears as deleted/closed.

      after downgrade the plugin all works again.

          [JENKINS-67502] cloudbees-bitbucket-branch-source latest version marks master branch as deleted

          Having the same issue

          Andrius Versockas added a comment - Having the same issue

          Arseniy Tashoyan added a comment - - edited

          Not only the master branch - any branch.
          Each time after 'git push', Jenkins marks the pushed branch as disabled (grey color, strike-through). No builds are executed anymore for this branch.
          Only after pressing "Scan Multibranch Pipeline Now" Jenkins enables the branch back and starts a build on it.
          The problem occurs with Bitbucket Branch Source plugin version 737.vdf9dc06105be. Workaround: downgrade the plugin to version 734.v2f848c5e6ea2.

          Arseniy Tashoyan added a comment - - edited Not only the master branch - any branch. Each time after 'git push', Jenkins marks the pushed branch as disabled (grey color, strike-through). No builds are executed anymore for this branch. Only after pressing "Scan Multibranch Pipeline Now" Jenkins enables the branch back and starts a build on it. The problem occurs with Bitbucket Branch Source plugin version 737.vdf9dc06105be. Workaround: downgrade the plugin to version 734.v2f848c5e6ea2.

          Please update to at least version 746.v350d2781c184

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

            Unassigned Unassigned
            igreenfield Izek Greenfield
            Votes:
            5 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: