Thank you! I should be able to get around this now that I know what's causing it.
On Thu, Apr 6, 2017 at 11:44 AM, Cesar Wong <cew...@redhat.com> wrote: > We don’t have an option to explicitly turn them off, but if you specify a > source ref other than ‘master’ in your build config, we don’t use —depth=1. > The ref can be a specific commit sha or the name of a branch. > > It sounds like an issue on the git server side… I know gogs had an issue > with this: https://github.com/gogits/gogs/issues/236 > > Copying Ben for awareness. > > On Apr 6, 2017, at 12:40 PM, Dean Peterson <peterson.d...@gmail.com> > wrote: > > I messed by copying and pasting; I needed two dashes in --recursiv. > > git clone --recursive --depth=1 https://peterson.dean%40gmail.com:p > ass%40word...@enterprisewebservice.kilnhg.com/Code/EnterpriseWebService/ > Openshift-Docker-Builds/wildfly-jdk-8.git > Cloning into 'wildfly-jdk-8'... > fatal: Authentication failed for 'https://peterson.dean%40gmail.com:p > ass%40word...@enterprisewebservice.kilnhg.com/Code/EnterpriseWebService/ > Openshift-Docker-Builds/wildfly-jdk-8.git/' > > Is there a way to get Openshift to not put the extra properties in the > clone command? It works without them at the command prompt, but fails > authentication with them. > > > On Thu, Apr 6, 2017 at 11:28 AM, Cesar Wong <cew...@redhat.com> wrote: > >> At least it shows the exact git clone command … can you try doing ‘git >> clone —recursive —depth=1 [the-url]’ from your local machine? >> >> I suspect that the —depth=1 may be what’s throwing it off >> >> On Apr 6, 2017, at 12:24 PM, Dean Peterson <peterson.d...@gmail.com> >> wrote: >> >> Thank you, that is helpful; >> >> It has been hung for about 5 minutes now. I have included the log in a >> gist: >> >> https://gist.github.com/deanpeterson/6b83f10ae100093f29b2530beb9de0fc >> >> Is there anything useful in there? >> >> On Thu, Apr 6, 2017 at 11:04 AM, Cesar Wong <cew...@redhat.com> wrote: >> >>> You can try setting the BUILD_LOGLEVEL env var to something high: >>> >>> $ oc set env bc/[your-bc] BUILD_LOGLEVEL=10 >>> >>> On Apr 6, 2017, at 12:00 PM, Dean Peterson <peterson.d...@gmail.com> >>> wrote: >>> >>> Yes, I can take that exact url and clone at the command line on windows >>> and on RHEL 7.3. It only takes about a second. On Openshift, it spins for >>> about 5-10 minutes then fails with that error. Is there a way to see the >>> entire error message? I can't seem to find it in any Docker of Openshift >>> logs. >>> >>> Thanks >>> >>> On Thu, Apr 6, 2017 at 10:51 AM, Cesar Wong <cew...@redhat.com> wrote: >>> >>>> Are you able to clone outside of openshift using that URL? >>>> >>>> Just looking at what the bad line length character being reported is >>>> (<!DO) my guess is that the git server is responding with an HTML doc/error >>>> of some kind. >>>> >>>> On Apr 6, 2017, at 11:43 AM, Dean Peterson <peterson.d...@gmail.com> >>>> wrote: >>>> >>>> Hi Cesar, >>>> >>>> VersionOpenShift Master:v1.4.1Kubernetes Master:v1.4.0+776c994 >>>> >>>> On Thu, Apr 6, 2017 at 10:19 AM, Cesar Wong <cew...@redhat.com> wrote: >>>> >>>>> Hi Dean, >>>>> >>>>> What version of openshift are you using? >>>>> >>>>> On Apr 6, 2017, at 11:07 AM, Dean Peterson <peterson.d...@gmail.com> >>>>> wrote: >>>>> >>>>> Hello, >>>>> >>>>> I just installed the latest version of Origin. A build that worked >>>>> before is failing with the following: >>>>> >>>>> Cloning "https://someone%40gmail.com:somepassword%40morepassword%40@ >>>>> enterprisewebservice.kilnhg.com/Code/EnterpriseWebService/Op >>>>> enshift-Docker-Builds/wildfly-jdk-8.git" ... >>>>> error: build error: fatal: protocol error: bad line length character: >>>>> <!DO >>>>> fatal: The remote end hung up unexpectedly >>>>> >>>>> I have verified that builds with public github urls work, but this url >>>>> that worked before is no longer working. >>>>> >>>>> Also, builds often hang on cloning, regardless for up to 5 minutes >>>>> before success or failing. >>>>> >>>>> Has something changed to prevent a url with escaped @ symbols in the >>>>> username/pass section from working? >>>>> >>>>> Thank you >>>>> _______________________________________________ >>>>> users mailing list >>>>> users@lists.openshift.redhat.com >>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
