Page History

...

1. Open the JIRA's Administration console.
2. Locate the TeamCity Configuration section and select Global Configuration.
   
3. Click Edit.
   

4. Configure the appropriate parameters, as follows:

   Parameter	Description	How to Optimize
   Connection Timeout

    - enter

   Enter timeout (in seconds) before connection to TeamCity server is established after

   accidental

   conneciton failure.

   Socket Timeout - timeout

   Connection timeout is used for establishing connection between JIRA and TeamCity. If the connectivity between two instances is intermittent, you can set the higher connection timeout for the add-on being able to successfully establish connection to TeamCity. If you set the lower value, the add-on will terminate the current connection attempt and start a new one.
   Socket Timeout	Timeout used for waiting data retireval from TeamCity server.	Once the add-on has established the connection, it starts waiting for data fetching from TeamCity. Socket timeout is amount time the add-on waits for completion of data retrieval from TeamCity instance before it terminates the session. The higher value you set, the longer the add-on will wait between transfer of consequent data packets.
   Response Timeout	Timeout

   - timeout

   before new connection to TeamCity server is established if no response has been received or completed.

   Index Depth - depth

   Response timeout is the time the add-on allocates to completion of the request and data transfer. If your builds are large, you can set the higher value to be sure that all data will be downloaded within this period.
   Index Depth	Depth of indexing builds depending on the recency of bulds (in days).

   Skip builds - allows

   By default, the add-on is configured to fetch all build data from TeamCity server, but you can change this parameter the appopriate age of build in days. For example, if you needn't data for the past two years, and you only need build data for the last 3 months - set '90'.
   Skip builds	Enables skipping builds that cannot be retrieved due to network or connectivity problems.	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 the indexing procedure, but skipped builds will not be available in JIRA.

5. Click Update.