Support ssh-keys to propagate build status to Bitbucket

[casareafer2908]

It would be simpler to set up Jenkins if the bitbucket-push-and-pull-request-plugin could support ssh keys to propagate the build status to bitbucket

As mentioned by @cdelmonte-zg in #108 , There is a limit while propagating the build status to bitbucket, propagation will work only if you are using, for the git plugin, credentials of the kind: "Username with Password".
#108 (comment)

I will research for other options, I just mention this as a "nice to have" feature.

[macghriogair]

This is actually a limitation of how the REST Api authentication with Bitbucket Server and Cloud works. I don't think this plugin can do anything about it.

Reference:

• https://developer.atlassian.com/server/bitbucket/how-tos/example-basic-authentication/
• https://developer.atlassian.com/bitbucket/api/2/reference/meta/authentication

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[derekatkins]

@macghriogair --

This is actually a limitation of how the REST Api authentication with Bitbucket Server and Cloud works. I don't think this plugin can do anything about it.

Reference:

* https://developer.atlassian.com/server/bitbucket/how-tos/example-basic-authentication/

* https://developer.atlassian.com/bitbucket/api/2/reference/meta/authentication

Indeed, the Rest API cannot use SSH credentials, however it would be useful if this plug-in could use OAuth Credentials (ala the bitbucket build status notifier plugin).