To clarify, I meant potentially a networking issue in terms of the openshift cluster SDN, not a networking issue in terms of connectivity on your host.Can you deploy our jenkins image ("oc new-app openshift/jenkins-1-centos7") and then use "oc rsh" to enter the running jenkins pod? From there you can attempt a git clone to ascertain whether things are working and possibly get a more useful error. You can also confirm that DNS resolution works properly from within that jenkins container (which should pretty much equate to the container environment the build is running in when it attempts to git clone).(there's nothing special about the jenkins image other than it's an image that you can easily run in a pod and then rsh into, and it has git pre-installed).--On Thu, Jan 21, 2016 at 5:34 PM, Dean Peterson <peterson dean gmail com> wrote:I don't think it is a networking issue. I can pull the repository using that exact url from the machine at the terminal. Yes, a public github repository works. I can also go to my older openshift setup, run the exact same template and it pulls the repository.On Thu, Jan 21, 2016 at 4:18 PM, Ben Parees <bparees redhat com> wrote:nothing should have changed...can you try a test w/ a public repo? wondering if it's a general networking issue.On Thu, Jan 21, 2016 at 4:35 PM, Dean Peterson <peterson dean gmail com> wrote:_______________________________________________
I just upgraded to v1.1.1 and I am no longer able to access my private git repositories:
builder.go:185] Error: build error: timeout while waiting for remote repository "https://username:password enterprisewebservice kilnhg com/Code/EnterpriseWebService/Openshift-Docker-Builds/wildfly-jdk-8.git
Did something change?
users mailing list
users lists openshift redhat com
--Ben Parees | OpenShiftBen Parees | OpenShift