Jenkins configuration

Overview

Several steps are required to configure Jenkins to integrate with your Bitbucket repo.

• Configuring Jenkins using either the Classic UI or the Blue Ocean plugin

• Configuring Bitbucket:

  1. Globally for all Jenkins instances

  2. Project or Repository hook settings

• Implementing General Settings or Advanced Configuration features depending on your development requirements.

To successfully use Webhook to Jenkins, the configuration process is made up of two parts:

• Your Jenkins instance

• Your Bitbucket project or repository

This document does not include detailed instructions regarding the initial setup of your Jenkins or Bitbucket instances. For more information regarding these topics, refer to the documentation on Bitbucket and Jenkins.

Before you start

Make sure that the following actions have been performed:

• Install either the Bitbucket Branch Source plugin or the Git plugin, depending on the option you and your organization use. Refer to the what plugin should I use page for more information.

• Install Webhook to Jenkins.

Global level

Adding an instance of Jenkins in Bitbucket makes configuring project-level and repository-level easier by allowing Webhook to Jenkins to use the entered Jenkins instance location as the default URL.

1. Log into your Bitbucket instance as an Administrator.

2. Click the Administration icon () in the top right corner to open the Administration page.

3. Under ADD-ONS, click Jenkins Servers.

   Open

   

4. (Optional) to add the instance from the project level or repository level only, open the appropriate window:

   1. Project Level: Select a project > Projects > Settings > Webhook to Jenkins for Bitbucket. For detailed instructions see, Project settings .

   2. Repository Level: Select the repository > Repositories > Settings > Webhook to Jenkins for Bitbucket. For detailed instructions see, Repository settings.

Add a new instance

1. Enter the Jenkins instance URL in the Jenkins Base field, your Jenkins Username and Password.

2. If you are using Git plugin version 4.11.4 or higher, the notifyCommit access token.
   See Access token requirements for Git plugin 4.11.4+ for information on how to generate the token. When using an earlier version of the Git plugin, the notifyCommit token is not required.

3. Decide if you want to Skip SSL certificate validation - Sometimes, self-signed certificates cause the client (Bitbucket) to deny all Jenkins requests. When selected, this option allows all certificates to be accepted, including self-signed certificates. Typically, this is used in test environments.

4. Select the performance mode: Live data or Cached data for Jenkins jobs.

   • Live data - Fetches job data from Jenkins in real time, ensuring that Bitbucket's latest updates are always displayed. However, this option might result in slower load times, especially for large number of jobs, as the data is retrieved fresh with each load.

   • Cached data - Stores Jenkins job data in Bitbucket's cache, allowing faster load times by refreshing the cached data every 10 minutes instead of fetching it in real time. While this improves performance, job updates are only reflected after the next cache refresh. Only jobs are cached, while builds and logs are retrieved in real time.

     Open

     

5. Click Save Instance.

When configuring Webhook to Jenkins at both the project and repository levels, the Jenkins instance URL is the default entry in the URL field.

Next steps

To add Jenkins instances on a project or repository level, go to:

• Project settings

• Repository settings

Further proceed to the Bitbucket configuration sections.