When setting up a job that uses the plugin, build notifications do not use the job specific Credentials. Instead, it uses the globally defined Credentials. If the globally defined credentials aren't the correct ones this result in an error message (the job finishes successfully).

Failed to post build status, additional information: Provided credentials cannot access the resource

In addition, the Bitbucket's "Required Builds" feature is unable to filter build-keys.

The solution should be to completely ignore the globally defined Credentials for the Bitbucket entry and always use the specific job credentials for:

• Fetching projects/repos during the job configuration (currently working).
• Installing Webhook (currently working)..
• Notifying job states to Bitbucket (currently not working).
• Integration with Bitbucket "Required Builds" build-keys filter (currently not working).

The above works if the globally defined Credentials are the same than the job defined Credentials.