How to integrate Bitbucket Server with Jenkins Pipelines

We have used several in the marketplace to meet our developers workflows, so far this one seems to work for most teams. Hopeful we can remove all the build/webhook plugins from our instances and reduce the overhead. Also this is being worked on by Atlassian, so as customers we may have more leverage to ask for features. What I am still having trouble with and maybe I am just over complicating it? I cannot figure out how to set the trigger value for the job in the in jenkins file.

If so, schedule some time, or let us know if there is a certain time that works best for you. In addition, you can add Bitbucket Server credentials (in the form of username and password) to make it easier for users to set up Jenkins jobs. Users will be able to choose from these credentials to allow Jenkins to authenticate with Bitbucket Server and retrieve their projects. We know that jenkins and bitbucket integration for many of our customers Jenkins is incredibly important and its integration with Bitbucket Server is a key part of their development workflow. Unfortunately, we also know that integrating Bitbucket Server with Jenkins wasn’t always easy – it may have required multiple plugins and considerable time. We began building our own integration, and we’re proud to announce that v1.0 is out.

Using the plugin

Right now, we’re working on a project to streamline Bitbucket’s CI workflow. The postwar German–Polish border ran along the Oder, separating the Dammvorstadt on the eastern bank – which became the Polish town of Słubice – from the rest of Frankfurt. While part of communist East Germany, Frankfurt was administered within Bezirk Frankfurt (Oder). It became part of the reconstituted state of Brandenburg with German reunification in 1990.

It is very useful to have the builds from Jenkins transferred in Bitbucket as issues, for example, if they have failed. The DevOps engineers might also need to track the successful builds, or the latest ones. This document on Setting up SSH for Git & Mercurial on Linux covers the details of what you need to do to be able to communicate between your build server and Bitbucket over SSH.


After you save, you’ll be taken to a page called Application Link details. It’s a good idea to keep this page open when moving onto part 2 so you can copy the details across to Bitbucket Server. Creating an Application Link to Jenkins enables additional functionality in Bitbucket Server. Watch our video to find out how to do this, or see below for written instructions.

jenkins and bitbucket integration

The DevOps process should be continuous and automated to be efficient. There are various software tools that DevOps engineers use and when they do not work together, the process becomes intermittent, slow, and prone to errors. With the help of Jenkins, organizations can significantly speed up software development, as it allows high levels of automation. It is an open-source tool written in Java and widely used by developers. All fields of the builds can be transferred, depending on your needs.

Override Repository URL

Do not forget to check “Build when a change is pushed to Bitbucket” in your job configuration. Select the triggers for the notifications., For instance, it makes sense to sell “On push“. The following plugin provides functionality available through
Pipeline-compatible steps.

Please feel free to email me at if you’d like us to help you explore your options. We have also released a demo on Youtube to quickly guide you through the process of setting up the plugin and creating a Jenkins pipeline. For example I would like to integrate the trigger into my jenkinsfile for my projects so that I can extend my config as code CI/CD model here. Jenkins will then automatically find, manage, and execute these Pipelines. Example of pipeline code for building on pull-request and push events. I have configured a pipeline in Jenkins that is correctly triggered by the plugin, but I can’t get this information to be processed in the pipeline.

Dsl Job actions for Bitbucket Push and Pull Request Trigger

Finally, in the Build Triggers section, select Poll SCM and set the poll frequency to whatever you require. Install the Bitbucket Post Webhooks plugin and navigate to the repository settings to configure the triggers. If you have feedback feel free to leave a comment on this Atlassian Community blog post.

  • The downside of it is that depending on how many repositories you have and how frequently you do the pooling, you might hit the Bitbucket Cloud API requests limits.
  • Then click the Create repository button to create a repo.
  • Bitbucket plugin is designed to offer integration between Bitbucket and Jenkins.
  • To run Jenkins with the plugin enabled you can spin up your Jenkins instance using java -jar jenkins.war in a directory that has the downloaded war-file.
  • Easily transfer jobs and builds from Jenkins to Bitbucket.

As it was mentioned in the first part of the tutorial, this pipeline will consist of several parts which will be triggered once a push on the bitbucket repo is made. We will also setup the webhook to let bitbucket inform Jenkins to start a new build on each push. Bitbucket helps developers store and manage their code, track versions and changes, and handle pull and push requests seamlessly.

Contribute to the plugin

For instructions on linking with Jenkins, see the documentation for the Bitbucket Server integration plugin for Jenkins on Once they’re linked, users can then complete the authorization process to perform Jenkins actions in Bitbucket. Part 4 (here)→ Create the second part of the AWS Infrastructure with Terraform. We are going to create the S3 buckets, the ECR repositories and complete the definition of the IAM roles by adding the correct policies. I’ve also tried not using the credentials manager and manually installing the keys in /var/log/jenkins/.ssh/, but to no avail.

jenkins and bitbucket integration

Another annoyance are the red bars and more failed jobs which results in polluted reports. Hello @Mikael Sandberg, Triggering on pull request open is not available right now however we are considering adding it in a future version. It’s like if Microsoft would decide not to use Google Chromium for their new Edge but creating the other the same thing from zero. You can then check the build info in Jenkins to see the changeset.

Running Jenkins with the plugin enabled

Many of the details you need to do this are on the Application Link details page mentioned in step 1. Wonderful, we could now download these files and check these reports if we would like to. We can always click on the Artifacts button on the top right to see the pipeline.log text file with the details of all the commands run in the pipeline. You can click on each step to see the details of the operations that have been performed in that given stage.