Child pages
  • Bitbucket Push And Pull Request Plugin

Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Plugin Information

View Bitbucket Push and Pull Request on the plugin site for more information.


This plugin requires a Jenkins v2.138.2 or later and supports the Bitbucket rest api v2.x+ and later.

The new features introduced by the Bitbucket Push and Pull Request plugin are:

  • support of pull requests
  • usage of Gson instead of net.sf.json.JSONObject (blacklisted starting from Jenkins 2.102+)
  • Introduction of models and security improvements

In which cases should I use this Plugin?

If you are using a Jenkins v2.138.2 or later, you may have some problems with the older Bitbucket plugin. This uses the JSONObject, already blacklisted by the JEP-200, causing an exception UnsupportedOperationException: Refusing to marshal net.sf.json.JSONObject for security reasons


In case you are using Bitbucket Cloud, configure your Bitbucket repository adding a webhook in the settings page. In the URL field (see image, point A) add your JENKINS_URL followed by "/bitbucket-hook/" (for example "") Credentials for the webhook endpoint are not required, the trailing slash is mandatory. For more infos please consult the resource

If you are using Bitbucket Server, follow the following steps:

  1. First install on the Bitbucket Server the Post Webhooks for Bitbucket plugin (it's free).
  2.  After that,  create from the repository settings a post-webHook and configure it as described for the Bitbucket Cloud.


GIthub releases

  • No labels