Page History

This page describes

How to Install the Plugin

Before installing the plugin make sure that you're using:

• JIRA 5 or higher
• TeamCity 6.x or higher.

First, you will need to configure your TeamCity instance:

1. Make sure that Rest API Plugin is enabled. To do that go to the following URL: <your-teamcity-server>/httpAuth/app/rest/application.wadl. You should see the output as shown below
   Image Removed
2. Configure integration with JIRA as described here. 
   Note: If you want to grant TeamCity access to all JIRA projects, click the Get All Projects link in the window Create New Issue Tracker Connection. Otherwise, specify the projects you want to grant access to in the Project Keys field as shown below. The JIRA user specified in the Username field should have access to relevant JIRA projects.
   Image Removed
3. Assign the  Project Viewer  and  Agent Manager  roles to an existing TeamCity user
    or 
   first create a new user and assign the roles.  

When you're finished with the steps above, switch to JIRA and do the following:

1. Install the plugin with Universal Plugin Manager  or  manually.
2. Install the plugin license:
   • If you generated a license on our site, install it in Administration > TeamCity Configuration > License Details.
   • If you generated a license on Marketplace, install it as described here. 
3. Create the TeamCity Application Link as described here. 
   Note: You don't need to create a link for every project. One Application Link will be enough. 
   Image Removed
   You will see your link in the Application Links list. 
   Image Removed
4. Configure Basic HTTP Authentication for Outgoing Authentication as described here. Use the credentials of the TeamCity user you configured earlier. These credentials will be used by the Application Link. 
   Image Removed   
   

...

See

...

the next pages for instructions on how to configure and manage TeamCity Integration for JIRA.

Immediately after installation, the plugin displays the TeamCity tab on the Project, Version and Issue pages in JIRA and starts indexing all TeamCity builds looking for those containing JIRA Issue Keys.

Note:   Issue Key  is a JIRA issue ID. Normally, it's specified in a commit log message in a version control system integrated with TeamCity. For example, a developer commits a source code file adding the log message  DEMO-5 Added compatibility with older browser versions,  the build that includes this change will be shown in JIRA in the DEMO project and in issue DEMO-5. 

While the plugin is analyzing the builds, you will see the the following message on the TeamCity tab.

Image Removed

Note:  This process may take a while on large instances.

When the inital indexing is over, you will see all found builds on the TeamCity tab on the Project (shown below), Version and Issue pages.

Image Removed

If no relevant builds are found, you will see the message No associated builds are found.  From now on, the plugin will update the build list in JIRA every 2 minutes.

Each issue in JIRA is assigned to a project and (optionally) to a version, therefore a build list displayed on the Project tab is compiled of the issues assigned to a given project, and a build list displayed on the Version tab is compiled of the issues assigned to a given version.

The TeamCity tab looks the same for issues, projects and versions. It contains the main build parameters, such as a start date, build duration, commit log, etc., and allows you to switch to TeamCity for detailed information.

Image Removed

How to Add the TeamCity Agents Gadget

The TeamCity Agents gadget shows whether the TeamCity agents are connected and enabled. You can add this gadget to your JIRA dashboard to have this information handy. If you're using the system dashboard which is displayed by default, you will need to create a custom dashboard and add the TeamCity Agents gadget.

Image Removed

You will see the gadget on your dashboard as shown below.

Image Removed