Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot clone a bundle from an SSH repo with custom port #490

Closed
mgryszko opened this issue Apr 12, 2017 · 8 comments
Closed

Cannot clone a bundle from an SSH repo with custom port #490

mgryszko opened this issue Apr 12, 2017 · 8 comments
Assignees
Labels
Milestone

Comments

@mgryszko
Copy link

mgryszko commented Apr 12, 2017

When trying to add a bundle in Antigen 2.0.0 with SSH Git protocol and custom port:

antigen bundle ssh://git@example.com:10022/group/repo.git

followed by antigen reset, I get this error in the log:

Cloning into '/Users/mgryszko/.antigen/bundles//git-example.com:10022-group-repo.git'...
fatal: No path specified. See 'man git-pull' for valid url syntax

The Git repository is an internal company repository managed by Gitlab. I removed the URL and the actual repo name due to confidentiality issues.

This was working in 1.4.1 so it's a regression bug for me.

@oli206
Copy link

oli206 commented Apr 12, 2017

Same issue here

@desyncr desyncr added the Bug label Apr 12, 2017
@desyncr desyncr added this to the 2.0.1 milestone Apr 12, 2017
@desyncr
Copy link
Member

desyncr commented Apr 12, 2017

I'm gonna look for a fix! Thank's for reporting!

@mgryszko
Copy link
Author

Can you have a look at #491 too for 2.0.1 milestone. Actually this issue resulted from the other one - instead of loading a bundle from a local filesystem I tried to load the bundle from Gitlab.

@desyncr
Copy link
Member

desyncr commented Apr 12, 2017

Work in progress here if you can take a look at it.

@desyncr
Copy link
Member

desyncr commented Apr 12, 2017

@mgryszko btw you may try

antigen bundle --url ssh://git@example.com:10022/group/repo.git

as a workaround.

@desyncr
Copy link
Member

desyncr commented Apr 13, 2017

Available in develop. Ready for 2.0.1.

@desyncr desyncr self-assigned this Apr 13, 2017
@oli206
Copy link

oli206 commented Apr 13, 2017 via email

@desyncr desyncr closed this as completed Apr 15, 2017
@mgryszko
Copy link
Author

Confirmed, working as expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants