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

Webhook does a scan for all refs instead only one from the payload

      I am getting rate limit issues due to this. Looking into Multibranch Pipeline Events - I can see every time Jenkins gets a payload, it does a scan on all the refs instead of the one it gets in the payload i.e.

                "type": "branch",
                "name": "name-of-branch", 

      The number of requests Jenkins makes to Bitbucket Server grows exponentially with a number of branches and pushes to them.

          [JENKINS-65909] Webhook does a scan for all refs instead only one from the payload

          Dee Kryvenko created issue -
          Dietmar Scheidl made changes -
          Remote Link New: This issue links to "PR (Web Link)" [ 26905 ]
          Kalle Niemitalo made changes -
          Link New: This issue is related to JENKINS-55071 [ JENKINS-55071 ]
          Dietmar Scheidl made changes -
          Assignee New: Dietmar Scheidl [ scddev ]
          Dietmar Scheidl made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Günter Grodotzki made changes -
          Link New: This issue is related to JENKINS-54983 [ JENKINS-54983 ]

          llibicpep, scddev was kind enough to provide a fix for this - can you please verify if it is looking better now?

          Günter Grodotzki added a comment - llibicpep , scddev was kind enough to provide a fix for this - can you please verify if it is looking better now?

          Since this issue seems to be the only change in v737 I'm dropping this here.
          Since I updated to v737 on our server receiving a webhook from BitBucket (Cloud) results in the branch that is changed being disabled, as if the branch was deleted and no build job being started started.

          Here's the observations so far:

          • No errors in Jenkins.log.
          • The webhook does arrive, but Multibranch Pipeline Events shows 0 branches were processed. Nothing about disabling branches though...
          • Running a Multibranch Pipeline scan re-enables the branch, finds the changes and starts a build as expected.
          • Rolling the plugin back to v434 makes everything work as expected again.

          Could it be that the patch here works for BitBucket server, but not for Cloud?

          Arjan Veenstra added a comment - Since this issue seems to be the only change in v737 I'm dropping this here. Since I updated to v737 on our server receiving a webhook from BitBucket (Cloud) results in the branch that is changed being disabled, as if the branch was deleted and no build job being started started. Here's the observations so far: No errors in Jenkins.log. The webhook does arrive, but Multibranch Pipeline Events shows 0 branches were processed . Nothing about disabling branches though... Running a Multibranch Pipeline scan re-enables the branch, finds the changes and starts a build as expected. Rolling the plugin back to v434 makes everything work as expected again. Could it be that the patch here works for BitBucket server, but not for Cloud?
          Günter Grodotzki made changes -
          Link New: This issue causes JENKINS-67502 [ JENKINS-67502 ]

          Martin Theiss added a comment -

          avee : Same issue happens randomly also with BitBucket (Server)

          Martin Theiss added a comment - avee  : Same issue happens randomly also with BitBucket (Server)

            nfalco Nikolas Falco
            llibicpep Dee Kryvenko
            Votes:
            5 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: