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

multi-branch pipeline not able to receive bitbucket push event



    • 2.1.1


      I tested the v2.1 plugin with the normal jenkins pipeline and all works fine, when it comes to multi-branch pipeline job, i can see in Bitbucket server it push the webhook to jenkins successfully on any code push, and in jenkins multi branch project log i can see logs like below:

      // code placeholder
      [Tue Sep 29 15:27:37 BST 2020] Received com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookConsumer$BitbucketSCMHeadEvent UPDATED event from bitbucket-auto-trigger-test with timestamp Tue Sep 29 15:27:37 BST 2020
      Found match against /folder1/job1
      Found match against /folder1/job2
      Found match against /folder2/job3
      Found match against /folder2/job4
      Found match against /folder3/jobN

      but it is very slow, looks like it is searching the whole jenkins instance's multi-branch pipeline jobs to do broadcast on the branch event and it stuck at some jobs, when i remove the problematic job it goes further but stuck at some other jobs again. I am wonder whether this is something handled by the Bitbucket Server Integration plugin or it is with multi-branch pipeline plugin.  If i put my test job into the folder it scans first, e.g. folder1, it works fine.  Can you please advise?


        Issue Links


            royxszhou2010 roy zhou created issue -
            mhenschke_atlassian Martin Henschke made changes -
            Field Original Value New Value
            Assignee Kristy Hughes [ khughes ]
            mhenschke_atlassian Martin Henschke made changes -
            Released As 2.1.1
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            kon Kalle Niemitalo made changes -
            Link This issue relates to JENKINS-63069 [ JENKINS-63069 ]


              Unassigned Unassigned
              royxszhou2010 roy zhou
              1 Vote for this issue
              3 Start watching this issue