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

Freestyle Job will not fire if "Bitbucket Server" selected in SCM

    XMLWordPrintable

Details

    Description

      Follow all configuration settings as described in this link:  https://plugins.jenkins.io/atlassian-bitbucket-server-integration/

      Push / PR, not fire freestyle job although it did work for a multibranch pipeline job ( not at the same time ).

      Changing from "Bitbucket Server" in SCM into "Git" did fire a job after Push / PR in Bitbucket.

       

      Plugin Version: Bitbucket Server Integration 3.3.2

      Steps :

      1. Configure Job as a descript here: https://plugins.jenkins.io/atlassian-bitbucket-server-integration/#plugin-content-select-a-bitbucket-server-instance-when-creating-a-freestyle-job
      2. Verify webbook is created ( see images below )
      3. Create PR 
      4. Freestyle Job should start to  build with 
      5. Triggered by Bitbucket webhook due to changes by Danil Shalumov.
        Running as SYSTEM

       

       

       

       

      Attachments

        1. screenshot-1.png
          screenshot-1.png
          32 kB
        2. screenshot-2.png
          screenshot-2.png
          90 kB
        3. screenshot-3.png
          screenshot-3.png
          96 kB
        4. screenshot-4.png
          screenshot-4.png
          41 kB
        5. screenshot-5.png
          screenshot-5.png
          36 kB

        Activity

          Hi Danil, thanks for your report. I'm assuming you're reporting that a freestyle job is not being fired after a push or pull request event is occurring in the repository the SCM is pointing to.

          Can you please provide the following details to this report:

          • The version of the plugin you are using
          • The exact steps you followed in setting up your freestyle branch setup, and your current configuration
          • The logging in Bitbucket showing the webhook being fired when a push or pull request event occurs
          • Logging in Jenkins (if there is any) of that webhook being received
          mhenschke_atlassian Martin Henschke added a comment - Hi Danil, thanks for your report. I'm assuming you're reporting that a freestyle job is not being fired after a push or pull request event is occurring in the repository the SCM is pointing to. Can you please provide the following details to this report: The version of the plugin you are using The exact steps you followed in setting up your freestyle branch setup, and your current configuration The logging in Bitbucket showing the webhook being fired when a push or pull request event occurs Logging in Jenkins (if there is any) of that webhook being received
          danils Danil added a comment -

          mhenschke_atlassian I update the bug content.

           

          danils Danil added a comment - mhenschke_atlassian I update the bug content.  

          Thanks for the response Danil. I've followed your replication instructions locally and was unable to reproduce the error.

          The screenshots you share all look normal- they show the webhook has registered successfully, has been submitted to Jenkins, which has responded with no error. That implies then that the head event generated by your webhook is not being picked up by the SCM.

          I have a few possible suggestions on where to go from here:

          • If the freestyle job has a build with the same head as the branch PR it won't need to rebuild. Have you tried pushing a new commit to the branch and determining if that kicks off a build?
          • Is your branch selector correctly configured? To test, try changing it to `**` and retrying the push
          • Is there anything in the logs? You could try tuning your system logging on to FINE and firing the webhook- if anything appears please share it on this ticket

          If all else fails can you please share your freestyle job configuration (with sensitive information redacted) so we can have a look and see what else might be the issue?

          mhenschke_atlassian Martin Henschke added a comment - Thanks for the response Danil. I've followed your replication instructions locally and was unable to reproduce the error. The screenshots you share all look normal- they show the webhook has registered successfully, has been submitted to Jenkins, which has responded with no error. That implies then that the head event generated by your webhook is not being picked up by the SCM. I have a few possible suggestions on where to go from here: If the freestyle job has a build with the same head as the branch PR it won't need to rebuild. Have you tried pushing a new commit to the branch and determining if that kicks off a build? Is your branch selector correctly configured? To test, try changing it to `**` and retrying the push Is there anything in the logs? You could try tuning your system logging on to FINE and firing the webhook- if anything appears please share it on this ticket If all else fails can you please share your freestyle job configuration (with sensitive information redacted) so we can have a look and see what else might be the issue?

          Hi Danil, I haven't heard a response on this ticket so I'll be closing this as cannot replicate.

          If the issue is persisting, you can reopen this issue with the request above. If there's sensitive information you need to share or you need more in-depth investigation, I'd recommend raising a ticket with support at getsupport.atlassian.com

          mhenschke_atlassian Martin Henschke added a comment - Hi Danil, I haven't heard a response on this ticket so I'll be closing this as cannot replicate. If the issue is persisting, you can reopen this issue with the request above. If there's sensitive information you need to share or you need more in-depth investigation, I'd recommend raising a ticket with support at getsupport.atlassian.com

          People

            Unassigned Unassigned
            danils Danil
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: