I wasn't going to say anything but I think I can explain what the issue possibly was since you mentioned Windows is in use.
I don't believe the Java stack works with the Windows networking layer at the same level. I have problems all the time with DNS lookups in our Java apps because our company configures the standard DNS search paths as part of the system configuration so that the full domain name is not required when hitting a service. For example our intranet can be reached by doing http://intranet/ because the domain is in the search path. This works fine for windows binaries that use the full windows networking stack but I must use the fully qualified name in Java. The same holds true for our database host names. In Microsoft's SQL Server Management Studio, I can use the host name of the database such as devdb1, but in Java connecting to the same database using JDBC, I must use devdb1.mycompany.com or it won't find it. I believe the same holds true for the DNS cache. DNS lookups in windows will utilize the cache if available even if the DNS service was having issues. The Java stacks don't use the Windows DNS cache. This explains why Jenkins wouldn't work but command-line did, even with the DNS service down. Just my $.02. On Fri, Dec 14, 2012 at 11:49 AM, Scott Evans <milwrd...@gmail.com> wrote: > In your jenkins build, can you try just running a command "nslookup" (or > ping would probably work too) on your agent machine to see what response > you get from actually within the build session? That might indicate > whether you're even getting a valid lookup back from DNS from within your > job environment. > > Might need to set up a new temp job which doesn't do any Git calls, etc. > to actually get to your build steps. > > Scott > > > > On Fri, Dec 14, 2012 at 7:09 AM, mwpowellhtx <mwpowell...@gmail.com>wrote: > >> The mystery still has me puzzled: Git Bash worked cloning, fetching, >> pulling. Yet Jenkins persistently failed even after repeated attempts >> restarting Jenkins Windows Service. It sounds plausible that Windows DNS >> Cache Service needed restarting, but then why did Git Bash work and Jenkins >> service did not? Are there any other services upon which Jenkins depends >> that might cause something like this? For now I've got an entry in my hosts >> file, but I still don't think I should have to do this, provided of course >> DNS is working right. >> >> > -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox <http://db.tt/9O6LfBX> !!
