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

Could not send notifications

XMLWordPrintable

      Description:

      After updating the Bitbucket Branch Source Plugin to 936.4.4, Jenkins fails to send build status notifications to our Bitbucket Server 7.0 instance (non–Data Center license).

      The error shows the plugin:

      {{[Bitbucket] Notifying commit build result
      ERROR: Could not send notifications
      java.io.FileNotFoundException: Resource http://<redacted>/rest/api/1.0/projects/BENCH/repos/fabric/commits/8eeb1fc3a8c662fd77451e6a3c1f24e97360e63a/builds not found}}

      This worked fine in previous plugin versions (e.g., 922.va_71d0e0b_7b_8d).
      After upgrading, all jobs fail to send commit build statuses back to Bitbucket.

      Environment:

      • Jenkins: 2.504.1 (LTS)
      • Bitbucket Server: 7.0.0 (Server license, not Data Center)
      • bitbucket-branch-source-plugin: 936.4.4 (failing)
      • bitbucket-branch-source-plugin: 922.va_71d0e0b_7b_8d (working)
      • OS: AlmaLinux
      • Java: 21.0.7+6-LTS

      Steps to Reproduce:

      1. Use Jenkins with Bitbucket Server 7.0 (non–Data Center).
      1. Upgrade bitbucket-branch-source-plugin to 936.4.4.
      1. Run a multibranch pipeline job linked to Bitbucket Server.
      1. Observe notification attempt in build logs.

            nfalco Nikolas Falco
            maduka14 Maduka Ariyasiri
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: