Comments
- 1-5 of 5
Chris,
Thanks for that. I'm very happy to create the key pair and the entry in known_hosts. In fact I did that already and had to hack the github url to reproduce the issue. The '/usr/bin/yes' thing is pretty funny. :)
I raised the bug more so you guys had some feedback. Given that the .deb package creates the 'cruise' user, I'd expect that that Cruise ought to verify that the cruise user has a fighting chance of connecting to GitHub (I guess the majority of your Git users would be using GH. Perhaps either creating the private key at package install time, and attempting to connect to GH? Or presenting the user with the steps you outline?
Best
J.
- Hi Ajay, You could specify multiple entries in the modification set: http://cruisecontrol.sourceforge.net/main/configxml.html#svn Mail me at the email address above your post if you want to go into more detail on this. Cheers Julian.
- John, Can you email me some more of the output please? medic (at) build-doctor {dot} com Thanks. Best Julian.
- Ian, The 'localWorkingCopy' attributes will need to point to the same directory in both the 'svnbootstrapper' and the 'modificationset' elements. Happy to talk more on this - suggest that you drop me a line via http://tinyurl.com/6yt3lk. Julian.
- Hi Ben, Thanks for the feedback. You're right: the SvnBootstrapper won't accept the useLocalRevision attribute. The Svn Modification Set will however accept that attribute. It's being used on a project with dozens of developers and its making a huge difference. I'll get the article updated asap. Thanks again. Best Julian.