Customers have installed this add-on in at least 338 active instances.
    by Kyle Nichollsfor Bitbucket Server 4.0.0 - 4.10.1 and more versions
    Versions available for Bitbucket Server 3.5.0 - 3.11.6
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    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

    Trigger parameterized builds in Jenkins from Bitbucket Server

    Trigger parameterized builds in Jenkins from Bitbucket Server

    Multiple Trigger Types

    Link your jenkins account to Bitbucket Server

    Manual Build Button

    Jobs can be triggered on branch and tag events, as well as pull request events.

    You can monitor specific paths or use pattern matching for branch names.

    Users can link there Jenkins account to Bitbucket Server. When they trigger a build via maunally, pushing, or pull requests the the build will be triggered using their Jenkins API token.

    A manual "Build in Jenkins" button will be added to the branch actions menu and to the pull request overview. If there are multiple jobs added with build parameters then developers can use which job to build.

    More details

    Jenkins base settings are configured on the admin page in Bitbucket or per project. Here you can setup the base URL for Jenkins and default authentication. Once this is setup you can start configuring and adding jobs in the Hook settings for a repository.

    Triggers inlcude:

    • Branch created (can use pattern matching for branches)
    • Push event (can use pattern matching for branches or file paths)
    • PR events (opened, re-opened, re-scoped, declined, merged)
    • Manual (adds a "Build in Jenkins" button to the branch action menus)
    • Branch deleted
    • Tag events

    Authentication for triggering a job can use one of 3 ways:

    • Jenkins API token via admin page
    • Job token via the hook settings
    • Jenkins API token via user profile page (per user)

    You can add build parameters (including token, string, choice, and boolean). You can also use a custom variable "$BRANCH". During the trigger event this value will be replaced with the branch that triggered the build.

    User reviews

    Sign in to write a review »
    by Felix Herzog on 2015-10-27
    Hi. Nice tool but sadly it mismatches one core requirement for our company: Nearly every project in our Enterprise has it's own Jenkins. With this Plugin you curently only can set up one Jenkins Base URL :/
    2 out of 2 found this review helpful
    Was this review helpful?YesNo

    Kyle Nicholls

    I know it has taken me a while, but I have just added support for Jenkins servers per project!



    Parameterized Builds for Jenkins isn't formally supported.


    Version 2.6.0 Bitbucket Server 4.0.0 - 4.10.1 Released 2016-10-15


    Bugfixes and new PR variables


    • Add additional variables to PR triggers: $PRID, $PRTITLE, $PRDESCRIPTION, $PRAUTHOR, $PRURL
    • support parameters with '=' in value
    • hide irrelevant variables when triggering a build ("$PRAUTHOR" becomes "" when triggering a build not associated with a pull request)


    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 Parameterized Builds for Jenkins 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 Parameterized Builds for Jenkins versions compatible with your instance, you can look through our version history page.

    Similar add-ons