If a build is configured to notify BitBucket when the build starts, and the build is then aborted, the BitBucket build status remains as 'In Progress'.

If another build of the same project is started for the same commit, a new build is started in BitBucket, but the status remains as 'In Progress.

This appears to be caused by the unique Jenkins build ID being used in the build key supplied to BitBucket.

It would be preferable to mark an aborted build as failed, and to overwrite the build status when another project build job starts for the same commit.