Page History

...

Indexing Options

Indexing options indicate how deep the add-on indexesTeamCity build data and whether it can skip builds upon error occurrence or should it attempt to fetch them. 

...

Issue Resolutions

Talk
id talk-189

...

I want to decrease the indexation time, what should I do?

You can use the Index Depth option, which allows you to define age of your builds that should be indexed. This option is useful when you need the indexed build data over the last 3 months, but not all the set of data.

Indexation freezes at a definite moment with no progress for a long period of time

...

.

Open the Troubleshooting page and enable logging of the com.stiltsoft.lib.teamcity.connector.rest package (For the details, refer to the this page).

On the Troubleshooting page, find the error that persists during the indexation.

1. If you encounter the Read timed out error, increase value of the Socket Timeout option. By default, 180 seconds are set.
2. If you encounter the com.stiltsoft.lib.teamcity.connector.rest.exception.ResponseTimeoutException: Response time is more than error, increase the value of the Response Timeout option.
3. If the issue still persists, after increasing values of the above mentioned options, enable the Skip Build option. If timeouts will be exceeded upon the next request, such a request will be skipped and will not be re-tried. Indexation will skip the current build and will proceed to the next build in the queue.

JIRA has run out of memory.

If you encounter this issue, follow these steps:

1. Increase the heap size of JVM (For the details, refer to this page).
2. Submit a ticket to our HelpDesk system.

What should I do if I use a proxy server?

If the TeamCity and JIRA servers do not operate in two different networks separated by the proxy server, you should set either the http.nonProxyHosts or the disableProxyForTeamcity parameter (For the details, refer to the this page)

You may encounter such an issue when you have a large change set with the merge of up to 5,000 commits. The add-on usually runs out of time to fetch data about this merge in the build.

You need to increase the response timeout up to 600 seconds, which should be enough for complete data retrieval.

Build indexation is reset and cannot be completed

1. The add-on fetches data from TeamCity in batches with 20 builds in each batch. Batches are fetched sequentially one by one. If the add-on fails to get the next batch with builds, the indexation is reset and the procedure starts from the beginning. You need to increase the socket timeout up to 180 seconds, so the add-on will be able to fetch the last batches in the queue. The connection timeout should be about 10 seconds.
2. You may encounter this issue if you perform daily backups with further suspension of TeamCity server during data backup. If you have a lot of data, the add-on is not able to index it all before backup creation, that’s why indexation is restarted each time. Disable the daily backup until completion of indexation.

After re-installation of the add-on, indexation starts from the very beginning and lasts for several days

Build data indexation is not persistent, so the add-on re-indexes the data upon update of the add-on itself. For large TeamCity servers, the complete re-indexation can take up to 3 days.