#Teamcity jira integration how to
#Teamcity jira integration install
#Teamcity jira integration code
#Teamcity jira integration password

The build status will be sent to Jira Cloud and displayed in the Jira task details. If you mention a Jira issue key in a VCS commit message, TeamCity will detect this message when running the build that contains this commit. TeamCity can report build statuses to Jira Cloud in real time. Reporting TeamCity Build Statuses to Jira Cloud This will allow TeamCity to retrieve the information about issues and display it in the UI. Note that a user specified in the connection to Jira should have sufficient permissions to view Jira issues. TeamCity will detect newly created projects in Jira and automatically synchronize the list of project keys. If the connection is successful, the Project Keys field will be automatically populated. You can also load all project keys automatically: enable Use all Jira projects automatically and test the connection to your Jira server. For example, if a project key is WEB, an issue key like WEB-101, mentioned in a VCS comment, will be turned into a link to the corresponding issue.

#Teamcity jira integration password

Ī username for self-managed Jira (specified in the Jira user profile) or email for Jira Cloud.Ī password for self-managed Jira or API token for Jira Cloud.Įnter a space-separated list of project keys to specify which strings should be recognized as references to issues in Jira. Specify the connection name to distinguish it from the other connections.Įnter the base URL of your Jira instance or server. To enable the integration, create a connection to Jira on the Project Settings | Issue Trackers page and specify the following settings: If the settings are different in a subproject, they have priority over the parent project's settings. Note that enabling integration for a project enables it for all its subprojects as well. TeamCity updates statuses of Jira issues displayed for builds every 10 minutes or when new commits are detected.Įnabling TeamCity integration with Jira requires Project Administrator permissions as it is configured at a project level. Mark fixed issues as Resolved in Jira to display them with the Fixed status in TeamCity logs (the time of resolve does not really matter). When committing changes to your version control, always mention the issue key related to the fix in the comment to the commit. You can filter the list to a particular range of builds and/or enable the Show only resolved issues option to display only issues fixed in the builds.įollow these recommendations to get the maximum benefit from the Jira integration: To view issues related to a whole build configuration (not only to individual builds), use the Issue Log tab of the Build Configuration Home page. Issues fixed in the build can be viewed on the Issues tab of the build results: To see the basic details of an issue in the TeamCity UI, open the Changes tab of the related build’s results and hover over the icon next to the issue key: It transforms these keys into links to the corresponding issues in Jira and displays them to TeamCity users in the UI. When integration with Jira is enabled, TeamCity automatically detects Jira issue keys mentioned in the comments of VCS commits. Displaying Links to Jira Issues in TeamCity UI

#Teamcity jira integration how to

This article describes how TeamCity behaves when integrated with Jira and contains instructions on how to enable and configure the integration. Reporting TeamCity build statuses to Jira Cloud. Support for the Git and Mercurial version control systems is bundled in with TeamCity 5.0.Displaying links to Jira issues in the TeamCity UI - applicable to self-managed Jira (Data Center and Server 4.4 or later) and Jira Cloud.

Users can view the status of a change across build configurations on a single page. Also, project archiving templates in version 5.0 put inactive projects out of site. In addition to its cloud support, version 5.0 also offers issue tracker integration with technologies like Jira and Bugzilla improved support for the Maven build management tool and build configuration templates to eliminate redundancies in build configuration settings.Ĭode coverage analysis has been improved for Java and.

#Teamcity jira integration code

TeamCity features unit testing, code quality analysis, and early reporting on build problems, JetBrains said.

#Teamcity jira integration install

This benefits users who perhaps do not want to install the TeamCity software in their own networks or do not have enough hardware to do so, Sher explained. “You can put TeamCity server and all agents on the cloud and TeamCity will start new agents, depending on current load,” said Pavel Sher, TeamCity project manager at JetBrains.