Public Site
- Provide a Name.
- Optionally, check the Auto enable new Jobs checkbox if you want to enable all Jobs on the site by default, including future new jobs.
- Select Public accessibility.
-
- In case you use SSL, make sure that Jira and Jenkins have each other SSL certificate in their trust store so that they can connect. See also Connecting to SSL Services.
-
- Provide the Sync URL that should be used for synchronization and other background actions.
- Optionally, provide a Display URL in case the Sync URL is not accessible by users and a different URL should be used in the UI features.
- Select an Authentication Method
- Select Sync Token Authentication to utilise JWT based authentication.
- This option requires version 4.0.0 of the Jenkins counterpart plugin or higher to be installed! You will also need to provide administrative credentials to register Jira with Jenkins.
- Select Basic Authentication to utilise username and token based authentication and provide them.
- If you use and external source (like LDAP, AD or Crowd) for authentication, then provide the API Token as password for the user.
-
Where to find the API Token...
The API Token is a password replacing token that users can use to authenticate with against Jenkins. This is mostly useful for users that have there accounts managed outside Jenkins. To get a token for an account, follow these steps:
- Login on Jenkins using the username and password of the synchronization account
- Click on the Account Name in the top-right corner of the page after login
- Then click on the Configure link in the left menu
- The API Token can now be displayed by clicking on the Show API Token… button
Private Site
Select this option if the Jira app can’t access the Jenkins site directly.
Private Jenkins sites will need to have Jira Integration for Jenkins - 3.6.0 or newer installed for the integration to work.
- Provide a Name.
- Optionally, check the Auto enable new Jobs checkbox if you want to enable all Jobs on the site by default, including future new
jobs.
- It is advised that you enable this, since jobs will only become available in Jira after Jenkins notifies Jira of it, and this can time some time depending the build workload on Jenkins.
- Select Private accessibility option if your Jenkins site is behind a firewall or otherwise not accessible for job and build synchronization.
- Provide the Display URL for UI features.
- Save the site and open the Configuration options of the Jenkins site by clicking on the Configuration action of the site.
- Follow the instructions in the dialog box to complete the registration of the site.
Jenkins will now notify Jira whenever there is a change that needs to be processed by Jira, so it may take some time for all
the jobs to become available in Jira.
Next: Getting Started