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.

Resources

Reviews for cloud

version:
Atlassian Bitbucket v4.10.1
parameterized build for jenkins 3.1.2
question:
I set a parameterized job to trigger a task of Jenkins job and the trigger is "push event".However the fact is that some developer can trigger it while the other couldn't when pushing code from local to the origin.

Hello,
The plugin is nice and easy to use. However it caused a problem when using with Bitbucket Data Center 5.1.3. When this plugin is active Pull Request Review screen cannot be rendered, all tabs are empty. I had to remove it.
Update: Version 3.1.1 solved the problem. It works perfectly. Thanks.

After evaluating several plugins for integration with Jenkins, this one was our choice. It offers a variety of trigger options, filters, and other options that can be configured to customize your hooks. Highly recommended.

Reviews for server

version:
Atlassian Bitbucket v4.10.1
parameterized build for jenkins 3.1.2
question:
I set a parameterized job to trigger a task of Jenkins job and the trigger is "push event".However the fact is that some developer can trigger it while the other couldn't when pushing code from local to the origin.

Hello,
The plugin is nice and easy to use. However it caused a problem when using with Bitbucket Data Center 5.1.3. When this plugin is active Pull Request Review screen cannot be rendered, all tabs are empty. I had to remove it.
Update: Version 3.1.1 solved the problem. It works perfectly. Thanks.

Reviews for Data Center

version:
Atlassian Bitbucket v4.10.1
parameterized build for jenkins 3.1.2
question:
I set a parameterized job to trigger a task of Jenkins job and the trigger is "push event".However the fact is that some developer can trigger it while the other couldn't when pushing code from local to the origin.

Hello,
The plugin is nice and easy to use. However it caused a problem when using with Bitbucket Data Center 5.1.3. When this plugin is active Pull Request Review screen cannot be rendered, all tabs are empty. I had to remove it.
Update: Version 3.1.1 solved the problem. It works perfectly. Thanks.

After evaluating several plugins for integration with Jenkins, this one was our choice. It offers a variety of trigger options, filters, and other options that can be configured to customize your hooks. Highly recommended.