Cause of RTC login failures from BF build execution?
Environment:
RTC 4.0.5 configured with IBM LDAP authentication. Build Forge 7.1.3.5 BF agent using RTC JBE 4.0.5 From the BF Step log: Java Version:I hilight the JDK as I just noticed this, but, looking at most recent successful build for same build definition: Java Version:The jbe -createPasswordFile was executed on March 7, 2014, but these build forge builds have been failing in similar fashion since having upgraded to RTC 4.0.5 from 4.0.3. I did take the steps of refreshing the BF project in two build definitions to update the properties to no improvement. |
One answer
we had a case recently of a similar problem. the project was Maven and needed a proxy (defined in the settings.xml) to get the dependencies resolved..
the step before this one in the ant file used the proxy and left it hanging in the environment, so the next command tried to use it.. boom..
we did
<setproxy proxyhost=""/>
in the build.xml before the failing step, see
https://jazz.net/forum/questions/144179/ant-task-startbuildactivity-fails-in-maven-build-after-dependencies-loaded-proxy-server-setting-solved
Comments
Kevin Ramer
commented Mar 26 '14, 10:00 a.m.
Hmm. So the "Not using a proxy to reach" message is false ?
sam detweiler
commented Mar 26 '14, 10:19 a.m.
no idea.. it might be true at the time the message was issued.. ours said using, not using, then boom..
another step used the proxy silently, and left the trash around.. not fun to debug
this might not be it, but sure sounds similar
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.