We have an issue with RTC polling when we have the proxy set in Jenkins. We need to set http and https proxy settings on the master for many other apps. So we do this in the Jenkins.xml file on the master. But this seems to break polling on RTC jobs. Jobs can still pull files out of source control but polling does not work. What is the difference between these 2 operations?
The following settings are set in the jenkins.xml:
-Dhttp.proxyHost=proxy001 -Dhttps.proxyHost=proxy001 -Dhttp.proxyPort=80 -Dhttps.proxyPort=80 -Dhttp.nonProxyHosts=*.ourcompanydomain.com
Our thoughts are that the IBM RTC Jenkins plug-in may not be respecting the nonProxyHosts java settings. Since our RTC instance is internal to the network, it should not feed the traffic destined for RTC through the proxy.
Any ideas, this one is killing us ! Any help would be greatly appreciated!!
Gives the below stack trace in the polling log:
FATAL: RTC : checking for changes failure: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.company.com:9443/ccm2/versionCompatibility?clientVersion=5.0. Error details: Remote host closed connection during handshake.
com.ibm.team.repository.common.transport.TeamServiceException: CRJAZ0099E An HTTP error occurred when this URL was being accessed: https://rtcserver.company.com:9443/ccm2/versionCompatibility?