In the command line I get this now:

Too many arguments.

usage: git clone [options] [--] <repo> [<dir>]

    -v, --verbose         be more verbose
    -q, --quiet           be more quiet
    --progress            force progress reporting
    -n, --no-checkout     don't create a checkout
    --bare                create a bare repository
    --mirror              create a mirror repository (implies bare)
    -l, --local           to clone from a local repository
    --no-hardlinks        don't use local hardlinks, always copy
    -s, --shared          setup as shared repository
    --recursive           initialize submodules in the clone
    --recurse-submodules  initialize submodules in the clone
    --template <template-directory>
                          directory from which templates will be used
    --reference <repo>    reference repository
    -o, --origin <name>   use <name> instead of 'origin' to track upstream
    -b, --branch <branch>
                          checkout <branch> instead of the remote's HEAD
    -u, --upload-pack <path>
                          path to git-upload-pack on the remote
    --depth <depth>       create a shallow clone of that depth
    --single-branch       clone only one branch, HEAD or --branch
    --separate-git-dir <gitdir>
                          separate git dir from working tree
    -c, --config <key=value>
                          set config inside the new repository


On Thu, Apr 6, 2017 at 11:28 AM, Cesar Wong <[email protected]> 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 <[email protected]>
> 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 <[email protected]> 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 <[email protected]>
>> 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 <[email protected]> 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 <[email protected]>
>>> wrote:
>>>
>>> Hi Cesar,
>>>
>>> VersionOpenShift Master:v1.4.1Kubernetes Master:v1.4.0+776c994
>>>
>>> On Thu, Apr 6, 2017 at 10:19 AM, Cesar Wong <[email protected]> wrote:
>>>
>>>> Hi Dean,
>>>>
>>>> What version of openshift are you using?
>>>>
>>>> On Apr 6, 2017, at 11:07 AM, Dean Peterson <[email protected]>
>>>> 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
>>>> [email protected]
>>>> http://lists.openshift.redhat.com/openshiftmm/listinfo/users
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
_______________________________________________
users mailing list
[email protected]
http://lists.openshift.redhat.com/openshiftmm/listinfo/users

Reply via email to