Environment:
Jenkins - 2.138.1
BlueOcean - 1.8.4
Bitbucket Branch Source - 2.2.12
Job Type: Bitbucket Server Pipeline

I have ran into this issue after upgrading BlueOcean from 1.8.3 to 1.8.4. Jenkins jobs were notifying Bitbucket when I was using BlueOcean 1.8.3, and the job logs had the following at the end of the pipeline:
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
However, after upgrading BlueOcean to 1.8.4, the Bitbucket plugin stopped notifying Bitbucket and the lines (from above) were missing from the log.

Feels like cause of the issue is because of an incompatible change upgrading to BlueOcean 1.8.4 and Bitbucket Branch Source plugin is not picking up the end of pipeline event.

Environment:
Jenkins - 2.235.5
BlueOcean - 1.23.2
Bitbucket Branch Source - 2.9.2
Job Type: Multibranch pipeline job

Issue:

The Build status in Bitbucket is Success even though the build has failed in Jenkins. Issue is occuring quite often now.

Could you please help us here?

Thanks in advance!

We face the same issue:

• Bitbucket Branch Source 2.9.6
• Bitbucket: v7.4.1
• Jenkins: 2.265

(Created an account just for this)

We also face the same issue:

• Jenkins 2.277.2
• Bitbucket Branch Source Plugin 2.9.8
• Atlassian Bitbucket v6.10.1

We also face the same issue:

• Jenkins 2.196
• Bitbucket Branch Source Plugin 2.4.4
• Atlassian Bitbucket v5.6.2

We also face the same issue:

• Jenkins 2.303.3
• Bitbucket Branch Source Plugin 2.9.11
• Bitbucket Server 7.17.4

Would you consider changing the priority of this bug, at least to major? It blocks people from, e.g., adopting merge checks and/or automating PR merges.

Does this also happen with the latest available version of the plugin?

We are also facing the same issue quite often. This blocks PRs to be merged having mandatory build check. Please increase the priority of this issue and provide a workaround. 

Environment:

Jenkins Version: 2.462.1
Bitbucket Branch Source Plugin Version: 888.v8e6d479a_1730
Job Type: Multibranch Pipeline
Bitbucket v8.19.8

Maybe the API call fails and therefor it remain in progress. If the API call fails and the build ends than we do nothing.
Do you have a look to the Jenkins logs?
Workaround is trigger a manual build.

nfalco, have a look at manually updating the Bitbucket build status. I've used this as a workaround in similar situations in the past.

https://developer.atlassian.com/server/bitbucket/how-tos/updating-build-status-for-commits/