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

The plugin we use for webhook setup is called "bitbucket-server-integration" and that was also upgraded from 2.1.2v to 3.3.2v as part of Jenkins upgrade and that broke triggering of jenkins pipelines.

      Hello,

      I am reaching out from Prudential USA company.

       


      Issue Summary:

      The plugin we use for webhook setup is called "bitbucket-server-integration" and that was also upgraded from 2.1.2v to 3.3.2v as part of Jenkins upgrade.

      Since the plugin got upgraded, the previously working webhook stopped working and any new commits to repo stopped triggering the Jenkins pipelines. We can see 200 response in webhook log but it still didn't fire and didn't trigger Jenkins Job.

       


      The work around we implemented is:

      We manually enabled the below option in Jenkins and then a new webhook got created by Jenkins in bitbucket with different name but same webhook URL and then the connection with Jenkins and Bitbucket will be reestablished.

      This fixed the webhook issue and pipelines got triggered whenever there is a new commit to repo. 

       

      Note: Now, after implementing this fix, there are two webhooks in the repo, although we noticed having two webhooks didn't cause any issue, we went ahead and deleted the older webhook (the one which shows NEVER FIRED) which is not needed anymore.


      Questions:

      1. Why the webhook stopped working after the plugin upgrade, is this issue related to https://issues.jenkins.io/browse/JENKINS-63071?
      2. The workaround we found is going to each pipeline and manually checking the checkbox option, but there are like more than 500 pipelines that we know and there may be more that we don't know. So, its not a easy and smart approach. How can we identify all the pipelines that are affected and fix them. Do you have any better solution?

       


      Please let me know if you need any further details. Looking forward to your response.

      Thank you for looking into this.

      Karra

       

       

          [JENKINS-71854] The plugin we use for webhook setup is called "bitbucket-server-integration" and that was also upgraded from 2.1.2v to 3.3.2v as part of Jenkins upgrade and that broke triggering of jenkins pipelines.

          Nihar created issue -
          Nihar made changes -
          Description Original: Hello,

          I am reaching out from Prudential USA company.

           
          ----
          h2. {color:#172b4d}Issue Summary:{color}

          The plugin we use for webhook setup is called "bitbucket-server-integration" and that was also upgraded from 2.1.2v to 3.3.2v as part of Jenkins upgrade.
           * [https://plugins.jenkins.io/atlassian-bitbucket-server-integration/{^}!https://confluence.prudential.com/images/icons/linkext7.gif|width=7,height=7!{^}]

          Since the plugin got upgraded, the previously working webhook stopped working and any new commits to repo stopped triggering the Jenkins pipelines. We can see 200 response in webhook log but it still didn't fire and didn't trigger Jenkins Job.

          !https://confluence.prudential.com/download/attachments/255172475/one%20webhook.png?version=1&modificationDate=1692421905000&api=v2!

           
          ----
          h2. {color:#172b4d}The work around we implemented is:{color}

          We manually enabled the below option in Jenkins and then a new webhook got created by Jenkins in bitbucket with different name but same webhook URL and then the connection with Jenkins and Bitbucket will be reestablished.

          This fixed the webhook issue and pipelines got triggered whenever there is a new commit to repo. 

          !https://confluence.prudential.com/download/attachments/255172475/workaround.png?version=1&modificationDate=1692420610037&api=v2!

           

          Note: Now, after implementing this fix, there are two webhooks in the repo, although we noticed having two webhooks didn't cause any issue, we went ahead and deleted the older webhook (the one which shows NEVER FIRED) which is not needed anymore.

          !https://confluence.prudential.com/download/attachments/255172475/200.png?version=1&modificationDate=1692420565913&api=v2!
          ----
          h2. {color:#172b4d}Questions:{color}
           # Why the webhook stopped working after the plugin upgrade, is this issue related to https://issues.jenkins.io/browse/JENKINS-63071?
           # The workaround we found is going to each pipeline and manually checking the checkbox option, but there are like more than 500 pipelines that we know and there may be more that we don't know. So, its not a easy and smart approach. *How can we identify all the pipelines that are affected and fix them.* Do you have any better solution?

           
          ----
          Please let me know if you need any further details. Looking forward to your response.

          Thank you for looking into this.

          Karra
          New: Hello,

          I am reaching out from Prudential USA company.

           
          ----
          h2. {color:#172b4d}Issue Summary:{color}

          The plugin we use for webhook setup is called "bitbucket-server-integration" and that was also upgraded from 2.1.2v to 3.3.2v as part of Jenkins upgrade.
           * [https://plugins.jenkins.io/atlassian-bitbucket-server-integration/\{^}!https://confluence.prudential.com/images/icons/linkext7.gif|https://plugins.jenkins.io/atlassian-bitbucket-server-integration/%7B%5E%7D!https://confluence.prudential.com/images/icons/linkext7.gif]

          Since the plugin got upgraded, the previously working webhook stopped working and any new commits to repo stopped triggering the Jenkins pipelines. We can see 200 response in webhook log but it still didn't fire and didn't trigger Jenkins Job.

          !https://confluence.prudential.com/download/attachments/255172475/one%20webhook.png?version=1&modificationDate=1692421905000&api=v2!

           
          ----
          h2. {color:#172b4d}The work around we implemented is:{color}

          We manually enabled the below option in Jenkins and then a new webhook got created by Jenkins in bitbucket with different name but same webhook URL and then the connection with Jenkins and Bitbucket will be reestablished.

          This fixed the webhook issue and pipelines got triggered whenever there is a new commit to repo. 

          !https://confluence.prudential.com/download/attachments/255172475/workaround.png?version=1&modificationDate=1692420610037&api=v2!

           

          Note: Now, after implementing this fix, there are two webhooks in the repo, although we noticed having two webhooks didn't cause any issue, we went ahead and deleted the older webhook (the one which shows NEVER FIRED) which is not needed anymore.

          !https://confluence.prudential.com/download/attachments/255172475/200.png?version=1&modificationDate=1692420565913&api=v2!
          ----
          h2. {color:#172b4d}Questions:{color}
           # Why the webhook stopped working after the plugin upgrade, is this issue related to https://issues.jenkins.io/browse/JENKINS-63071?
           # The workaround we found is going to each pipeline and manually checking the checkbox option, but there are like more than 500 pipelines that we know and there may be more that we don't know. So, its not a easy and smart approach. *How can we identify all the pipelines that are affected and fix them.* Do you have any better solution?

           
          ----
          Please let me know if you need any further details. Looking forward to your response.

          Thank you for looking into this.

          Karra

           

           

          Hi Karra, thank you for the report and apologies in the delay in responding to it.

          We are currently exploring this issue and will respond to this ticket once we have a good understanding of the issue and a possible solution to the bug itself. Regarding attempting to identify and fix pipeline files, I recommend if you haven't already to raise a ticket at https://support.atlassian.com/bitbucket-server/, as they will be best positioned to help you with this issue.

          Martin Henschke added a comment - Hi Karra, thank you for the report and apologies in the delay in responding to it. We are currently exploring this issue and will respond to this ticket once we have a good understanding of the issue and a possible solution to the bug itself. Regarding attempting to identify and fix pipeline files, I recommend if you haven't already to raise a ticket at https://support.atlassian.com/bitbucket-server/ , as they will be best positioned to help you with this issue.

          Hi again Karra,

          We've done an investigation of this issue, and following the proceeding steps we were unable to replicate this issue:

          • Started with version 2.204.1 of Jenkins and then version 2.1.2 of the plugin.
          • Used Bitbucket DC 8.15.0-SNAPSHOT from master.
          • Connected Bitbucket to Jenkins and also did an applink.
          • Created a repo with a mock Jenkins file in master branch.
          • Created a pipeline job for the master branch of the repo.
          • Added a webhook trigger for ref changes.
          • Verified manual build works.
          • Verified that ref change webhooks can trigger builds (push to the master branch).
          • Upgrade plugin version to 3.2.2 and Jenkins version to 2.289.1
          • Verified that existing builds were still in the history
          • Verified manual build still works.
          • Verified that ref change webhooks can still trigger builds (push to the master branch).

          Could you please review the steps we took and verify if the upgrade path you performed differed from it, and if so in what way, so we can re-attempt replication. Also, if you haven't already, please reach out to support to resolve the existing job configuration issue.

          Thanks,

          Martin

          Martin Henschke added a comment - Hi again Karra, We've done an investigation of this issue, and following the proceeding steps we were unable to replicate this issue: Started with version 2.204.1 of Jenkins and then version 2.1.2 of the plugin. Used Bitbucket DC 8.15.0-SNAPSHOT from master. Connected Bitbucket to Jenkins and also did an applink. Created a repo with a mock Jenkins file in master branch. Created a pipeline job for the master branch of the repo. Added a webhook trigger for ref changes. Verified manual build works. Verified that ref change webhooks can trigger builds (push to the master branch). Upgrade plugin version to 3.2.2 and Jenkins version to 2.289.1 Verified that existing builds were still in the history Verified manual build still works. Verified that ref change webhooks can still trigger builds (push to the master branch). Could you please review the steps we took and verify if the upgrade path you performed differed from it, and if so in what way, so we can re-attempt replication. Also, if you haven't already, please reach out to support to resolve the existing job configuration issue. Thanks, Martin

          Sunny added a comment -

          Closing this issue after investigation and cannot be reproduced. 

          If the issue persists or is encountered again, please reach out to Atlassian support.

          Sunny added a comment - Closing this issue after investigation and cannot be reproduced.  If the issue persists or is encountered again, please reach out to Atlassian support.
          Sunny made changes -
          Resolution New: Cannot Reproduce [ 5 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            Unassigned Unassigned
            nkarra Nihar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: