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

Bitbucket Multibranch Pipeline: Scan triggers all builds regardless of any changes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • bitbucket-branch-source-plugin
    • Jenkins: 2.150.1 LTS
      Bitbucket Branch Source Plugin: 2.3.0
      Pipeline Multibranch Plugin: 2.20
      Installation: Windows 2016 Server (Used windows installer)
      Proxy: None
      Browser: Chrome Version 71.0.3578.98 (Official Build) (64-bit)

      I currently have a Bibucket Mercurial Multibranch pipeline that scans every 5 minutes for any PRs submitted against master which triggers our build for those branches.

      After updating our Bitbucket Branch Source plugin version from 2.2.12 to 2.2.15, some scans would periodically result in retriggering all of our PR builds even though none of those PRs were updated.

      This has a tremendous impact as all of our Jenkins agents would overload with unnecessary builds.

      I recently updated the Bitbucket Branch Source plugin version to 2.3.0 (most recent release) hoping this had been fixed and it's still a problem.

      This issue appears to have been introduced in version 2.2.13. I'm reverting back to 2.2.12 until this issue is fixed.

       

        1. image-2019-01-30-08-34-53-641.png
          image-2019-01-30-08-34-53-641.png
          73 kB
        2. PRBuilds.PNG
          PRBuilds.PNG
          39 kB

          [JENKINS-55517] Bitbucket Multibranch Pipeline: Scan triggers all builds regardless of any changes

          German Pineda created issue -
          German Pineda made changes -
          Environment Original: Jenkins: 2.150.1 LTS
          Bitbucket Branch Source Plugin: 2.3.0
          Installation: Windows 2016 Server (Used windows installer)
          Proxy: None
          Browser: Chrome Version 71.0.3578.98 (Official Build) (64-bit)           		New: Jenkins: 2.150.1 LTS
          Bitbucket Branch Source Plugin: 2.3.0
          Pipeline Multibranch Plugin: 2.20
          Installation: Windows 2016 Server (Used windows installer)
          Proxy: None
          Browser: Chrome Version 71.0.3578.98 (Official Build) (64-bit)
          German Pineda made changes -
          Summary Original: Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes New: Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes
          Vivek Pandey made changes -
          Labels Original: plugin New: pipeline-triaged plugin

          Bart Devriendt added a comment - - edited

          We are having this problem also in 2.4 version of the plugin with git repositories.  Sometimes all builds are started although no changes were made to a branch/PR.  In the log of the scan every branch is stated to have changes.

          We reverted to 2.2.12 as well

          Bart Devriendt added a comment - - edited We are having this problem also in 2.4 version of the plugin with git repositories.  Sometimes all builds are started although no changes were made to a branch/PR.  In the log of the scan every branch is stated to have changes. We reverted to 2.2.12 as well
          German Pineda made changes -
          Attachment New: image-2019-01-30-08-34-53-641.png [ 45840 ]

          German Pineda added a comment -

          This is starting to become a bigger issue for us since keeping the Bitbucket Branch Source plugin at version 2.2.12 is now causing dependency issues with Blue Ocean (see picture below):

          For anyone else experiencing this problem, you might need to hold back on updating Blue Ocean as well until this issue is fixed.

           

          German Pineda added a comment - This is starting to become a bigger issue for us since keeping the Bitbucket Branch Source plugin at version 2.2.12 is now causing dependency issues with Blue Ocean (see picture below): For anyone else experiencing this problem, you might need to hold back on updating Blue Ocean as well until this issue is fixed.  

          Michael Kriese added a comment -

          Looks like the 'Ignore rebuilding merge branches when only the target branch changed' option is no longer working.

          Michael Kriese added a comment - Looks like the 'Ignore rebuilding merge branches when only the target branch changed' option is no longer working.
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-62669 [ JENKINS-62669 ]

          Jesse Glick added a comment -

          Candidate for closing: JENKINS-62669

          Jesse Glick added a comment - Candidate for closing: JENKINS-62669

            nfalco Nikolas Falco
            germanpineda German Pineda
            Votes:
            5 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: