1,224
Customers have installed this add-on in at least 1,224 active instances.
    by Tomas Bjerrefor Bitbucket Server 4.4.0 - 4.14.3 and more versions
    Versions available for Bitbucket Server 2.12.0 - 4.3.3
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.
    Get it nowFree add-on

    Notify other systems about events regarding pull requests in Bitbucket Server

    Notify other systems about events regarding pull requests in Bitbucket Server

    Variables

    Different URL:s for different filters

    Custom buttons in pull request view

    Highly configurable URL:s with variables. You ca, for example, trigger Jenkins like this

    http://server/job/name/buildWithParameters?token=T&FROM_REPO= ${PULL_REQUEST_FROM_REPO_NAME} &TO_REPO= ${PULL_REQUEST_TO_REPO_NAME}

    Each notification has 2 fields to construct a filter. The filter has a text field and a regexp. When the regexp matches the text, the notification is triggered. Use any variable(s) to construct text to match on.

    It can add buttons to the pull request view in Bitbucket. And bind them to notifications. To for example trigger a build manually.

    A pressed button will fire a BUTTON_TRIGGER -event.

    More details

    Invoke custom URL:s, supporting variables, when configured events occur on pull requests in Bitbucket Server. Can notify Jenkins, Bamboo, TeamCity, HipChat... and many more!

    • Trigger on one, or several, event(s) regarding pull requests including source branch change and target branch change.
    • Add custom buttons to pull request view in Bitbucket Server.
    • Invoke one, or several, URL(s) when event(s) are triggered.
      • Optionally with "HTTP Basic Authentication" headers.
      • Completely custom URL supporting variables, including but ot limited to:
        • ${PULL_REQUEST_ID} Example: 1
        • ${PULL_REQUEST_VERSION} Example: 1
        • ${PULL_REQUEST_AUTHOR_ID} Example: 1
        • ${PULL_REQUEST_FROM_HASH} Example: 6053...
        • ${PULL_REQUEST_FROM_ID} Example: refs/heads/branch
        • ${PULL_REQUEST_FROM_REPO_ID} Example: 1
        • ${PULL_REQUEST_FROM_REPO_PROJECT_ID} Example: 1
        • ${PULL_REQUEST_FROM_REPO_PROJECT_KEY} Example: PROJECT_1
        • ${PULL_REQUEST_FROM_REPO_SLUG} Example: rep_1
        • ...

    More details on GitHub and this blog post.

    User reviews

    (21)
    Sign in to write a review
    by Daniel Sobral on 2017-03-08
    Handles everything I throw at it.
    Was this review helpful?YesNo
    by Joshua Shearer on 2017-01-31
    The plugin's source is available on Github, and the author accepts contributions and feature suggestions from the community. Contains very useful functionality for integrating Bitbucket into the rest of your infrastructure. Almost all of this functionality should be built into Bitbucket directly.
    Was this review helpful?YesNo
    by Mark de Bont on 2017-01-24
    Nice, allows to start Bamboo builds on creating/(re)opening Pull Requests instead on every push from a developer
    Was this review helpful?YesNo
    by Ali Hesson on 2017-01-06
    Can this plug-in be used to trigger builds when new commits are made to the Pull Requests? If we are using Jenkins, how does it differ than the Webhook to Jenkins for Bitbucket plug-in?
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    Tomas Bjerre

    Yes it can trigger builds in Jenkins when new commits are made to pull requests.

    To do a correct verification you should trigger on changes to the target branch, and the source branch. And you should merge source into target before compiling and running tests. This plugin can provide the information needed to do that. And not only in Jenkins. People are using it with Bamboo and TeamCity as well.

    It is well documented at Github so you should find your answers there: https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket

    by Kashyap Parikh on 2016-11-22
    Very useful to integrate several hundred repos with distributed CI systems. Tomas is very responsive. We have had issues upgrading the plugin from 1.x to 2.x while upgrading underlying Stash from 3.x to Bitbucket 4.x and Tomas provided quick fixes in succession to make the upgrade work. I wish Atlassian change the plugin from UNSUPPORTED to SUPPORTED. So far I haven's seen any other plugin that provide similar functionality and Bitbucket doesn't provide these features out of box.
    Was this review helpful?YesNo

    Pricing

    Basic support resources are available for this add-on.

    Vendor support resources

    Documentation

    Find out how this add-on works.

    Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this add-on.

    Versions

    Version 2.61 Bitbucket Server 4.4.0 - 4.14.3 Released 2017-03-25

    Summary

    Rendering variables in injection URL

    Details

    GitHub #208 Injection URL does not allow variables

    Rendering variables in injection URL

    Installation

    1. Log into your Bitbucket instance as an admin.
    2. Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Pull Request Notifier for Bitbucket via search. Results include add-on versions compatible with your Bitbucket instance.
    5. Click Install to download and install your add-on.
    6. You're all set! Click Close in the Installed and ready to go dialog.

    To find older Pull Request Notifier for Bitbucket versions compatible with your instance, you can look through our version history page.

    Similar add-ons