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

The Bitbucket Server Integration plugin for Jenkins does not always report build status

      When everything works as expected we see something like this in the log of a Jenkins build:

      Posting build status of INPROGRESS to Bitbucket Server for commit id [18590112a773ec5a48f5c89c16de99d3fb16d903] and ref 'refs/heads/working'

      When the build finishes up we see something like this in the log:

      Posting build status of SUCCESSFUL to Bitbucket Server for commit id [18590112a773ec5a48f5c89c16de99d3fb16d903] and ref 'refs/heads/working'

      Sometimes we can even see Jenkins trying several times to report the result to the Bitbucket Server.

      The problem is that sometimes we do not even see Jenkins trying to report any build status to the Bitbucket Server, not when the build starts and not when it ends.

      We do quite consistently see that one of our multibranch-pipeline-job does not report build status to the Bitbucket Server, but a down-stream job triggered from that  same pipeline, using the same repo and Branch Sources configuration, does report build status to the Bitbucket Server.

      We cannot yet upgrade the plugin from 3.6.0 to 4.x due to the bug reported in JENKINS-72120.

          [JENKINS-72573] The Bitbucket Server Integration plugin for Jenkins does not always report build status

          Hello cb2 
          Sorry to hear you have problems. This doesn't sound quite like a bug but more like an environmental issue and one that is better resolved via our support team. Could you please open a support request, be sure to include a support-zip (from Bitbucket) and the logs from Jenkins as the response code and a little bit of more information is available in the logs that is not written to the user via the build log.

          Daniel Kjellin added a comment - Hello cb2   Sorry to hear you have problems. This doesn't sound quite like a bug but more like an environmental issue and one that is better resolved via our support team. Could you please open a support request, be sure to include a support-zip (from Bitbucket) and the logs from Jenkins as the response code and a little bit of more information is available in the logs that is not written to the user via the build log.

          Hello dkjellin, thanks for responding to this.

          Due to the problem with version 4.0.0 of the plugin (JENKINS-72120) we have switched to using https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/ instead. So unless someone else is seeing this I think we close the ticket.

          Christer Blomqvist added a comment - Hello dkjellin , thanks for responding to this. Due to the problem with version 4.0.0 of the plugin ( JENKINS-72120 ) we have switched to using https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/ instead. So unless someone else is seeing this I think we close the ticket.

          Scott added a comment -

          We recently switched from  https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/ to this plugin, and I think I can shed more light on this issue.

           

          When Jenkins fails to check out the branch from git then the build status isn't reported. The Cloudbees plugin always reports status, even on checkout failure. It is a big pain for my company and frankly is the biggest downside of the Bitbucket Server plugin. So please fix this!

          Scott added a comment - We recently switched from   https://plugins.jenkins.io/cloudbees-bitbucket-branch-source/ to this plugin, and I think I can shed more light on this issue.   When Jenkins fails to check out the branch from git then the build status isn't reported. The Cloudbees plugin always reports status, even on checkout failure. It is a big pain for my company and frankly is the biggest downside of the Bitbucket Server plugin. So please fix this!

          Can added a comment -

          We also have the same problem. In some branches we get build status in some branches we dont. Its a huge problem since developers must have successful builds to approve and merge. Please escalate this problem. We are using plugin version 4.1

          Can added a comment - We also have the same problem. In some branches we get build status in some branches we dont. Its a huge problem since developers must have successful builds to approve and merge. Please escalate this problem. We are using plugin version 4.1

          Jakub Glazik added a comment -

          For anybody with the problem on plugin 4.1.0, please check, if this is not your case for PR build statuses:
          https://issues.jenkins.io/browse/JENKINS-74782

          Jakub Glazik added a comment - For anybody with the problem on plugin 4.1.0, please check, if this is not your case for PR build statuses: https://issues.jenkins.io/browse/JENKINS-74782

            Unassigned Unassigned
            cb2 Christer Blomqvist
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: