...
| Property | Value | Description |
|---|---|---|
disableProxyForTeamcity | true / false | If true, the add-on will try to directly connect to all Teamcity servers without using the proxy server. If all your TeamCity servers operate within the same network, this parameter will allow JIRA to establish direct connection to all TeamCity servers. |
http.nonProxyHosts | host name | If specified, the add-on will try to directly connect to the specified TeamCity servers, the proxy server will be used for the rest of hosts. This parameter allows you to indicate which TeamCity servers JIRA can establish direct connection to and which instances operate via a proxy server. |
...
| Info |
|---|
| For the details on JIRA startup options, refer to the How to Configure an Outbound HTTP and HTTPS Proxy for JIRA page. |
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.
...
Open the Troubleshooting page and enable logging of the com.stiltsoft.lib.teamcity.connector.rest package (For for the details, refer to the this page).
...
- Increase the heap size of JVM (For for the details, refer to this page).
- Submit a ticket to our HelpDesk system.
...
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 for the details, refer to the this page).