On this page:
This feature is available for Jira Server only. |
Starting from version 2.2.0, TeamCity Integration for Jira app allows you to manage the TeamCity Build Runner custom field. It allows you to remotely run builds on TeamCity server from Jira.
Before proceeding to configuration of this custom field, please refer to the documentation about management of custom fields in Jira.
Once you have configured and added the custom field, you can remotely run builds in TeamCity from Jira.
Users will be able to change the default branch configured for the field once they decide to run a build in an issue. |
You can add one or multiple build parameters into configuration of the custom field.
For example, if you want to add one parameter with the value so you have to specify the following:
teamcity.agent.name=teamcity_agent_name |
teamcity.agent.name=Windows2012R2;issue_key=$JIRA_KEY |
If you want to run a chain of linked builds within the same branch but from a different build configuration, use the following parameter in the property set:
reverse.dep.*.teamcity.branch.name=$BRANCH_NAME |
If you want to pass the issue key to TeamCity for mapping the build to the specific issue, add the following property:
issue_key=$JIRA_KEY |
For the list of accepted build parameters, see TeamCity documentation. |
The teamcity.build.branch parameter (if used not for a chain of linked builds) is deprecated since TeamCity Integration for Jira 2.7.0 and will be ignored. |