Don't know what happened. Turns out it was a strange DNS issue (as folks pointed out). What makes it strange is why it would fail for Jenkins and still succeed for a command line Git Bash.
To workaround I added an entry in my hosts file and that has "fixed" at least my part of the issue. Still in question is whether whatever DNS services are up and running properly. On Thursday, December 13, 2012 6:05:04 PM UTC-6, mwpowellhtx wrote: > > No, Jenkins is running on the same machine as my day to day development. > Not the best of ideas I know. > > For the second part, yes, I can clone from a command line or Git Bash. > > On Thursday, December 13, 2012 5:44:40 PM UTC-6, Andrew Melo wrote: >> >> I mean, presumably the machine you work on day to day isn't the machine >> your Jenkins slaves run on (since it seems like you have a larger install) >> >> If you SSH to your Jenkins master/slaves, can you clone from them? >> >> ---- >> Andrew Melo >> Sent from my secret fortress. >> >> On Dec 14, 2012, at 0:17, mwpowellhtx <mwpow...@gmail.com> wrote: >> >> How do you mean, "connect to your slaves, clone manually"? From a command >> line or Git Bash? Yes, I can clone manually with the same (copy and paste) >> SSH URI. >> >> On Thursday, December 13, 2012 4:33:12 PM UTC-6, Andrew Melo wrote: >>> >>> On Thu, Dec 13, 2012 at 11:24 PM, mwpowellhtx <mwpow...@gmail.com> >>> wrote: >>> > And I can assure you it's not. I copy and paste the exact same address >>> on >>> > the command line, and I can clone from the command line. Only Jenkins >>> is now >>> > consistently failing across the board for jobs that were previously >>> > succeeding. >>> > >>> > We're speculating whether repositoryhosting.com (our host) has some >>> limits >>> > set on SSH. >>> >>> This seems to look like your DNS isnt resolving the host name right, >>> it's not (necessarily) a matter of you fumbling the hostname... >>> >>> stderr: ssh: <repo-host/>: no address associated with name >>> fatal: Could not read from remote repository. >>> >>> If you connect to your slaves, can you do a git clone manually? >>> >>> > >>> > >>> > On Thursday, December 13, 2012 3:59:42 PM UTC-6, SA Evans wrote: >>> >> >>> >> The error would indicate to me that it can't find the host where your >>> repo >>> >> is, whether a typo in that variable setting that's not getting >>> resolved >>> >> through your nameserver, or some sort of network issue, most likely. >>> >> >>> >> >>> >> >>> >> On Thu, Dec 13, 2012 at 3:47 PM, mwpowellhtx <mwpow...@gmail.com> >>> wrote: >>> >>> >>> >>> To clarify, I've edited the actual names out. The names are there, >>> it was >>> >>> working earlier. Now suddenly it has stopped working. >>> >>> >>> >>> A colleague of mine and I are wondering whether it's a SSH thing, or >>> >>> perhaps there's a limit set by our host, or something. >>> >>> >>> >>> On Thursday, December 13, 2012 3:43:44 PM UTC-6, mwpowellhtx wrote: >>> >>>> >>> >>>> I'm not sure what you mean. Can you be more specific? It's possible >>> >>>> something got unset, but like I said, it was working all day until >>> just now. >>> >>>> >>> >>>> On Thursday, December 13, 2012 3:38:27 PM UTC-6, SA Evans wrote: >>> >>>>> >>> >>>>> Looks like you're missing an environment setting for repo-host >>> >>>>> >>> >>>>> Scott >>> >>>>> >>> >>>>> On Thu, Dec 13, 2012 at 3:35 PM, mwpowellhtx <mwpow...@gmail.com> >>> >>>>> wrote: >>> >>>>>> >>> >>>>>> stderr: ssh: <repo-host/>: no address associated with name >>> >>>>> >>> >>>>> >>> >> >>> > >>> >>> >>> >>> -- >>> -- >>> Andrew Melo >>> >>
