[New Feature] Build notifications not sent to BitBucket for manually triggered builds

[cdelmonte-zg]

Discussed in #228

^{Originally posted by banjoh June 29, 2020}
At times builds fail due to some flaky environment problem which is inevitable. Such builds may end up being marked as failed or unstable. To resolve this, one might restart the build manually to get the build to pass. Unfortunately the build status does not get updated.

According to https://support.atlassian.com/bitbucket-cloud/docs/integrate-your-build-system-with-bitbucket-cloud/, it does not look like there are any specific environment variables that could be missing for manually triggered builds.

Is there a way to have the plugin handle manually triggered builds for the purpose of build notifications to BB? Currently we have a separate script that does this for us.

Environment

Jenkins: 2.235.1
BPPP: 2.4.0

PS: I can submit a patch if need be, but I'd need some pointers of what needs to be done

[y0zg]

This feature is really needed to make CICD flow more robust in case of any failures