RTC 4.5 uDeploy V6.0.1 : Build Engine ERROR: peer not authenticated
Accepted answer
The error in your second post,
java.lang.Exception: Request error:500
is a backward compatibility issue identified here, https://jazz.net/library/article/1395. The workaround at the time was to avoid using pattern matching. The best solution available now though is to upgrade UCD as you have done.
Sorry for the inconvenience,
Scott
2 other answers
Comments
I install a whole new instance of udeploy server with v6.0.1.4 ifix 01. Everything else works fine except
the "peer not authenticated" error come back.
Please ignore my previous comment. It causes by my build engine to udeploy Server network issue.
Hi Joseph,
Are you still having issues? If so, could you please try a few things to help debug this?
1. Open up a defect describing your problem, here.
2. Add this property to your build definition, set the value to true, and run another build. Then attach the build log to the work item.
team.udeploy.debug=true
3. What version of the Build System Toolkit are you using?
4. Does the Test Connection button work in the Post-build Deploy tab of your build definition?
Scott
I did still get "peer not authenticated" frequently when build on remote Windows XP server. I submit 10 requests, 6 of them success and 4 fails with "peer not authenticated" when push the build artifact to uDeploy server.
Finally, I found the slow build time was caused by the invalid domain name server on the remote build server. After fixing the DNS setting, the build time reduce from 56 mins to 22 secs.