Learn more about Jira Cloud products, features, plans, and migration.
Integrate Jira Cloud with Confluence, development tools, apps, and self-hosted tools using OAuth and feature flags.
Control who has access to your Jira Cloud products and give them the right permissions to perform their role.
Learn how to set up, customize, and manage Jira Cloud projects.
Explore issues, issue types, issue custom fields, issue screens, custom field context, and issue field configurations in Jira Cloud.
Define the lifecycle of your work and learn about issue workflow schemes and the issue collector.
Learn more on how you can set up Jira Cloud for your team.
This integration provides a free, easy, secure, and reliable way to connect your Jenkins server, running behind the firewall, with either Jira Software Cloud or Jira Service Management Cloud.
This gives your team more visibility and context on every issue in Jira, showing the latest build status or if your work has been successfully deployed to an environment.
You can also use this information to search across issues using the Jira Query Language (JQL), answering questions like “Which issues in the current sprint have been deployed to production?” You can even add these as quick filters on your boards!
Check the following things before you connect Jenkins to Jira Software Cloud:
You're a site administrator of your Jira Cloud site.
You're an admin in Jenkins and you can install, update, and delete plugins.
You can edit the Jenkinsfile in your source code/repo for the pipelines you want to use this integration with.
Your team is including issue keys (e.g. FUSE-123) in their commit messages (for deployment information) and branch names (for build information). If your team isn't already doing this, learn more about referencing issues in your development work.
Link Jira Software Cloud with Jenkins
Install the Jira Cloud plugin for Jenkins
Log in to your Jenkins server and navigate to the Plugin Manager.
Select the “Available” tab and search for “Atlassian Jira Software Cloud”.
Install the plugin.
The open-source plugin is hosted at GitHub. You can check it out here.
Install the “Jenkins for Jira” app in Jira
You can install the "Jenkins for Jira" via the Jira Marketplace:
Log in to your Jira site and go to Apps > Explore more apps.
Type "Jenkins for Jira" into the search box.
Click on the "Jenkins for Jira by Atlassian" app (if it doesn't show up, you might have to remove the "Top trending" filter).
Click on "Get app".
Set up a webhook in Jira
After installing the "Jenkins for Jira" app on your Jira site, you’ll need to set up a webhook:
In Jira, go to Apps > Manage your apps.
In the left sidebar, under "Apps", click the link to the "Jenkins for Jira" app.
Click on "Connect a Jenkins server".
The app will remind you to install the Jenkins plugin. Click on "Next".
Enter a name for your Jenkins server.
Copy the webhook URL for later use.
Copy the secret for later use.
Connect Jenkins to the webhook
With the webhook URL and secret, you can now create a connection between Jenkins and Jira.
In Jenkins, go to Manage Jenkins > Configure System and scroll to the Jira Software Cloud Integration section.
Select Add Jira Cloud Site > Jira Cloud Site. New fields will appear for your site name, webhook URL, and secret.
Enter the following details:
Site name: The URL for your Jira Cloud site, for example yourcompany.atlassian.net.
Webhook URL: The webhook URL you copied from the Jenkins app in Jira earlier.
Select Add > Jenkins
For Kind, select Secret text.
For Secret, paste the secret you copied from the Jenkins app in Jira earlier.
For Description, provide a description that helps you identify the secret.
The secret should now show in the dropdown menu. Select your newly created secret.
Select Test connection to make sure your credentials are valid for your Jira site.
Use the Jira cloud plugin for Jenkins
This plugin will send build and deployment events to Jira so that they’re visible in your Jira issues, on the deployments timeline, and in the Releases feature.
To send information from Jenkins to Jira, your team must include Jira issue keys (e.g. FUSE-123) in their commit messages (for deployment information) and branch names (for build information). Whenever a pipeline runs in Jenkins, the plugin will look for Jira issue keys in the branch name and commit messages. If it finds issue keys, it will send build and deployment information to Jira. If it doesn’t find issue keys, the Jenkins plugin won’t send anything to Jira.
Sending builds automatically
To automatically send build events without having to add anything to your Jenkinsfiles, go to Manage Jenkins > Configure System and enable the checkbox “Sends builds automatically”.
When you enable this, the plugin will send an "in progress" build event to Jira once a pipeline run has started and a "success" or "failure" build event once the pipeline has finished successfully or stopped due to an error.
If you also specify a regular expression for builds, the plugin will only send a build event to Jira once a build step with a matching name has been finished.
The regular expression ^build$ would match the build stage in the following Jenkinsfile, for example:
Whenever the pipeline in this Jenkinsfile runs, it will send build events to all configured Jira Cloud sites on start and finish of the build stage.
Sending deployments automatically
To automatically send deployment events without having to add anything to your Jenkinsfiles, go to Manage Jenkins > Configure System and enable the checkbox “Sends deployments automatically”.
When you enable this, the plugin will send an "in progress" deployment event to Jira once a build step with a name matching the specified regular expression has started, and a "success" or "failure" deployment event once that build step has finished.
For this to work, the deployment steps in your Jenkinsfile must contain the environment name in their name. The regular expression must contain the fragment (?<envName>.*) to match the environment name so that the plugin can extract the environment name from the build step names.
Let's look at an example Jenkinsfile:
If the checkbox "Send deployments automatically" is enabled and the regular expression is set to ^deploy to (?<envName>.*)$, a run of the above Jenkinsfile will send "in progress" deployment events for the stg and prod environments to all configured Jira Cloud sites, followed by respective "success" deployment events once the build steps are finished.
Sending builds explicitly
If you want more control over when to send build events, you can use the jiraSendBuildInfo build step:
This will send a "success" or "failure" build event to all configured Jira Cloud sites after the Build stage has finished successfully or with an error. The Jenkins plugin will automatically extract Jira issue keys from the branch name.
You can also specify a Jira site URL and instruct the plugin to only send build events to this Jira site (rather than to all configured Jira sites).
Sending deployments explicitly
If you want more control over when to send deployment events, you can use the jiraSendDeploymentInfo build step:
This will send a "success" or "failure" deployment event to all configured Jira sites at the end of the stages Deploy - Staging and Deploy - Production.
You must provide the parameters environmentId, environmentName, and environmentType. The environmentType must be one of the following: unmapped, development, testing, staging, production.
You can provide the parameter site to specify to send the deployment events to a single Jira site instead of all configured Jira sites.
When multiple Jira sites are connected to a Jenkins server, the site parameter is required for jiraSendDeploymentInfo with enableGating:true. More details about Deployment Gating can be found here.
You can also specify a branch with the branch parameter to define the branch from which to extract Jira issue keys to connect the deployments with.
Example of a complete Jenkinsfile
You can mix build and deployments as in the Jenkinsfile below:
View development information in Jira
Whenever you make a commit or merge a pull request in a connected source code management tool, like Bitbucket or GitHub, it should run the Jenkins pipeline you have specified for that repo. The development panel on your Jira issues will update to show any associated build and deployment information, as long as your team is including issue keys in their pull requests, commit messages, and branch names. Learn more about how to view development information for an issue.
If you’ve enabled the deployments feature in your Jira project, the Deployments page will show all your Jenkins deployments on a timeline. You can filter or search to view your deployments by environment, assignee, issue type, and more. And if your team is using releases and versions to organize your work, you’ll also find deployment information in the Releases feature.
Link Jira Service Management Cloud with Jenkins
Was this helpful?