Use Issue Log of a build configuration to get issues related to builds turn on the " Show only resolved issues" option to only display the issues fixed in the builds. Resolve issues when they are fixed (the time of resolve does not really matter). When committing changes to your version control, always mention the issue ID (issue key) related to the fix in the comment to the commit. To get maximum benefit from the issue tracker integration, do the following:
Recommendations on Using Issue Tracker Integration Since TeamCity 2020.1, integration with Jira Cloud also allows previewing build statuses directly in Jira. You can filter the list to a particular range of builds and view issues mentioned in comments with their states. Issues fixed in the build can also be viewed on the Issues tab of the build results. When an integration is configured, TeamCity automatically transforms an issue ID (=issue key in Jira, work item ID in Azure DevOps Server) mentioned in the VCS commit comment into a link to the corresponding issue, and the basic issue details are displayed in the TeamCity web UI when hovering over the icon next to the issue ID (for example, on the Changes tab of Build Results).
The Supported Platforms and Environments page lists supported versions. TeamCity supports Jira, Bugzilla, YouTrack, GitHub, GitLab, Bitbucket Cloud, and Azure DevOps Server (formerly TFS) trackers out of the box. You can configure integration if you have multiple projects on both the TeamCity and the issue tracker server or if you are using different issue trackers for different projects.Įnabling integration for the project also enables it for all its subprojects if the configuration settings are different in a subproject, its settings have priority over the project's settings. The integration is configured at the project level: the Project Administrator permissions are required. TeamCity detects issues mentioned in the comments to version control changes, turning them into links to your issue tracker in the TeamCity UI. Default value is 60 minutes.Īutomatic proxy detection + minor bug fixes.Ĭommunication with Mend servers is now encrypted using SSL by default.TeamCity can be integrated with your issue tracker to provide a comprehensive view of your development project. Connection timeout is measured in minutes. Resume build upon failed communication to server.Īdded support for user-level access control in integrations.Īdd parameter to enable/disable Mend plugin (SKIP_Mend_PLUGIN = true ).īug Fix - Fail or error : Build did not pass despite the flag set to false.Īdd 'fail on error' functionality - fails the build even in case of inventory force update, or other general errors.Īdd support for force check all dependencies (old and new) according to the organization policiesīug Fix - use global settings in maven runner.Īdd connection timeout parameter. Service URL supports both with and without "/agent" ( , ) Upgraded the XStream Core dependency to version 1.4.12įix TeamCity build error issue - opened on GitHub.
Teamcity jira integration upgrade#
Upgrade junit dependency version to 4.13.1 As displayed in the following screenshot, once the checkbox is selected, newly displayed fields can be filled in, in order to allow communication with the Mend servers. Proxy Server (optional): If TeamCity is behind a firewall then you should select the checkbox. If the field is left blank, the value is 60 minutes. Service URL: URL of the environment on which the Mend organization is hosted. The default is “ ” therefore organizations hosted on that can leave this field blank.Ĭonnection Timeout (optional): Connection timeout value in minutes. Policy Check: Checks that the introduced open source libraries conform with organization policies.Ĭheck only new libraries: Check that the newly introduced open source libraries conform with organization policies.įorce check all libraries: Check that all introduced open source libraries conform with organization policies.ĭisable: Disable policies check when updating Mend.įorce Update: Updates organization inventory regardless of policy violations.įail on Error: I ndicates whether or not to fail the build on a general error (e.g. See User Level Access Control in Integrations and APIs for more information. You can retrieve it in the Admin Integration API page. Organization Token: A unique identifier of the organization.
0 kommentar(er)
