...
This option allows the add-on to skip builds that cannot be retrieved due to some connectivity issues. Instead of performing continuous attempts to index the build, the add-on will skip it and proceed to the next build in the queue. It can speed up the indexing procedure, but skipped builds will not be available in JIRA.
...
Issue Resolutions
| Talk | ||
|---|---|---|
|
Build indexation freezes on some percentage with no progress for a long time
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
- 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.
- 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
// todo описать
...если нужно еще что-то сделать.