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

Jenkins build notifications creates a new build state instead of updating the existing one on Bitbucket

XMLWordPrintable

      Successful builds after a failed build on the same commit, are send to Jenkins, but do not mark the build in Bitbucket as complete.
      The builds are shown as two individual builds with the failed one sorted higher.

      This appeared after https://issues.jenkins.io/browse/JENKINS-75083

      Happens on Bitbucket Server v8.19.8

       

        1. image-2025-01-13-09-39-54-300.png
          image-2025-01-13-09-39-54-300.png
          31 kB

          [JENKINS-75116] Jenkins build notifications creates a new build state instead of updating the existing one on Bitbucket

          Nikolas Falco added a comment - - edited

          For bitbucket server we have replace deprecated endpoint with new one. This means that PR started with older plugin version could be recognized by the server as different because we valued the refname attribute.
          By the atlassian documentation refname should not be part of the build status notification but at least on cloud seems to be so, that why it duplicates build status notification (when I test it).
          If this happens also for fresh new PRs than I will investigate otherwise I will close the issue. Let me know.

          EDIT: I suppose this is the cause because new PR post additional informations like build duration that I see in the second build status. Instead the first build status does not have

          Nikolas Falco added a comment - - edited For bitbucket server we have replace deprecated endpoint with new one. This means that PR started with older plugin version could be recognized by the server as different because we valued the refname attribute. By the atlassian documentation refname should not be part of the build status notification but at least on cloud seems to be so, that why it duplicates build status notification (when I test it). If this happens also for fresh new PRs than I will investigate otherwise I will close the issue. Let me know. EDIT: I suppose this is the cause because new PR post additional informations like build duration that I see in the second build status. Instead the first build status does not have

          Nikolas Falco added a comment -

          As workaround you can decline the PR and reopen

          Nikolas Falco added a comment - As workaround you can decline the PR and reopen

          Carsten added a comment -

          Thank You I will check.

          Carsten added a comment - Thank You I will check.

          Carsten added a comment -

          We checked and found actually a hidden manual notification call on our side using the old endpoint.
          I guess that issue was then caused by our code.

          Sorry for the inconvenience and thx for your quick reply.

          Carsten added a comment - We checked and found actually a hidden manual notification call on our side using the old endpoint. I guess that issue was then caused by our code. Sorry for the inconvenience and thx for your quick reply.

            nfalco Nikolas Falco
            sol23 Carsten
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: