The latest JIRA TeamCity Integration Plugin supports JIRA 5.x-6.x.
The latest JIRA TeamCity Integration Plugin supports TeamCity 6.x-8.x.
No. That is why when you restart JIRA, the plugin needs to index all TeamCity builds from scratch.
The plugin installs on JIRA and shows TeamCity builds in JIRA. It doesn't work the other way round.
Most likely your JIRA user doesn't have the permission to View Issue Source Tab.
If the plugin doesn't show builds that you're sure should be shown, reindex the build list completely. To do that, go to Administration > Add-ons > TeamCity Configuration > Troubleshooting and click the Reindex button. Please note that reindexation will start from scratch and can take a while on large instances.
It may take quite a long time, if your TeamCity server has lots of builds. However, if you feel that it takes longer than it should, please go to Administration > Add-ons > TeamCity Configuration > Troubleshooting and see if there're any errors.
Go to Administration > Add-ons > TeamCity Configuration > Troubleshooting.
These are the most frequent problems with possible causes:
Error Message | Possible Cause |
---|---|
java.net.NoRouteToHostException: No route to host | The TeamCity host can't be reached due to network problems and/or an intervening firewall. |
java.net.SocketException: Connection reset | A TCP error. Most likely, a wrong port specified for the TeamCity host. |
java.net.SocketTimeoutException: Read timed out | The JIRA host connected to the TeamCity host but didn't get any response from it most likely due to network problems. |
com.stiltsoft.lib.teamcity.connector.rest.exception.HttpStatusNotOkException: HTTP/1.1 401 Unauthorized | The TeamCity user's password in the Application Link is not valid.For other HTTP errors (those containing HTTP/1.1 [message code] ), please refer to Status Code Definitions . If you need further assistance in case of errors, please contact us. |
You don't need a Project Link for the plugin to work. With the Application Link correctly configured, the plugin will assign all builds containing Issue Keys to corresponding projects.
You need to set this parameter -DdisableProxyForTeamcity=true
on your Java virtual machine startup. Learn more about parameters here.
Initially, the plugin indexes builds by packages of 20 builds. If during the initial indexation, the plugin can't access TeamCity, it will keep trying to index the build package next to the last successfully indexed one. If the Skip Builds option is enabled in Administration > Add-ons > TeamCity Configuration > Global Configuration, the plugin will skip the builds that can't be indexed due to network or other problems.
After the initial build index is created, the plugin updates it every 2 minutes. In case it can't connect to TeamCity, the plugin will keep trying to reach it every 2 minutes until it succeeds. If the Skip Builds option is enabled in Administration > Add-ons > TeamCity Configuration > Global Configuration, the plugin will skip the builds that can't be indexed due to network or other problems.