SOLVED, I think. While I SAID I set the owner of the files in the .ssh directory to SYSTEM, I had forgotten to set the owner of the private key. Sheesh. So I set the owner to SYSTEM. I ran another build yesterday before I left work and it succeeded. I'll need to examine the results, but I suspect it will be good results.
The JFrog-Artifactory documentation for using ssh keys rather stinks, but I figured it out. I get that they didn't want to go too deeply into the process, but they might have pointed me at some Windows - SYSTEM docs that described how this is done. Further, JetBrains handles code checkout differently, and better. With TeamCity, there's no need to learn where to put keys and known_hosts files and such on EACH AGENT. I had hoped the Artifactory plugin would work with TeamCity, and deal with the code in the same manner. -- View this message in context: http://forums.jfrog.org/Artifactory-release-management-git-ssh-TeamCity-Windows-tp7580727p7580729.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140 _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
