Once the add-on has been installed and application links have been configured, indexing of TeamCity data begins. Indexing is required for correct output of all related data about build in corresponding JIRA's sections. Indexing is performed only once for each configured application link. Afterwards the add-on synchronizes data with TeamCity servers every two minutes.
Percentage of data indexing is counted depending on the number of TeamCity servers being not indexed. For example, if you have only one TeamCity server connected, so 100% are equal to complete data indexing of this server. So if you see in the interface that 40% were completed, so 40% of data from TeamCity have been indexed. If you have two TeamCity servers and both are not indexed, so 100% are divided by two, with 50% per each TeamCity server. For example, if data from one server is 80% indexed, and data from the other is one 10% indexed, so the total indexation percent for both instances will be 45% ((80%+10%)/2). |
You can also monitor progress of indexing and see if any errors occurred during the procedure.
Here you can see status of indexing for each configured application link with TeamCity. For each application link, the following information is available:
You can restart the indexing procedure, by clicking Reindex.
If you experience any issues with data indexing, here you can also find out errors that occurred during indexing. For each error, the following information is displayed:
To clear all error messages, click the Clear button.
If you experience any issues with data indexing, please supply the error and its description when posting a ticket to our HelpDesk system. Below you can find the table with errors and their description.
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, an incorrect port was specified for the TeamCity host. |
java.net.SocketTimeoutException: Read timed out org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 10000 ms |
|
com.stiltsoft.lib.teamcity.connector.rest.exception.HttpStatusNotOkException: HTTP/1.1 401 Unauthorized |
|
com.stiltsoft.lib.teamcity.connector.rest.exception.HttpStatusNotOkException: HTTP/1.1 502 Proxy Error or com.stiltsoft.lib.teamcity.connector.rest.exception.HttpStatusNotOkException: HTTP/1.0 403 Forbidden | JIRA tries to connect to TeamCity via a proxy. See #8 below. |
com.stiltsoft.lib.teamcity.connector.rest.exception.HttpStatusNotOkException: HTTP/1.0 404 Not Found | The add-on cannot reach the TeamCity host by the specified URL in the application link. Ensure that you have specified the correct address of the TeamCIty server. How to verify URL address of TeamCity address:
|
java.net.UnknownHostException | IP address of the specified host cannot be resolved. Ensure that the host specified in the application link is accessible.
|
HTTP/1.1 503 Service Unavailable | TeamCity server is temporarily unavailable. This may happen due to high load on the server or due to any other problem. Try to open TeamCity server in your browser. Address the issue to TeamCity administrator to check the service unavailability. |
For other HTTP errors (those containing HTTP/1.1 [message code]), please refer to Status Code Definitions.