Push to private git repo #10

Closed
meenarc opened this Issue Mar 21, 2013 · 6 comments

Comments

Projects
None yet
2 participants
@meenarc

meenarc commented Mar 21, 2013

Is there an override option that lets me specify a private git repo url to push this to?

@miketheman

This comment has been minimized.

Show comment
Hide comment
@miketheman

miketheman Mar 22, 2013

Owner

@meenarc I don't think I understand - the plugin will push to whichever git repo is configured to use, and release the completed cookbook to the community site.

You can change which git remote is used with the --remote flag - is that what you're looking for?

You may also wish to run git remote -v locally in your cookbook directory to see where your git repo is currently pointing to.

Owner

miketheman commented Mar 22, 2013

@meenarc I don't think I understand - the plugin will push to whichever git repo is configured to use, and release the completed cookbook to the community site.

You can change which git remote is used with the --remote flag - is that what you're looking for?

You may also wish to run git remote -v locally in your cookbook directory to see where your git repo is currently pointing to.

@meenarc

This comment has been minimized.

Show comment
Hide comment
@meenarc

meenarc Mar 22, 2013

Maybe am doing something wrong .
I tried the --remote flag like this.I listed the contents of git remote -v. Ensure I had push permissions and I am on master branch
So I do a knife community release <cookbook_name> --remote https://myprivate-repo-ip:8443/git/dev-repo.git --no-site-share
And I get ERROR: The remote/branch specified does not seem to exist.

meenarc commented Mar 22, 2013

Maybe am doing something wrong .
I tried the --remote flag like this.I listed the contents of git remote -v. Ensure I had push permissions and I am on master branch
So I do a knife community release <cookbook_name> --remote https://myprivate-repo-ip:8443/git/dev-repo.git --no-site-share
And I get ERROR: The remote/branch specified does not seem to exist.

@miketheman

This comment has been minimized.

Show comment
Hide comment
@miketheman

miketheman Mar 23, 2013

Owner

I think you may be passing the wrong argument to the --remote flag.

Here's what you may see from a git remote -v run:

$ git remote -v
origin  git@github.com:miketheman/knife-community.git (fetch)
origin  git@github.com:miketheman/knife-community.git (push)

In this case, I can see that the remote name is origin, and if I wanted to pass this to knife-community, I would use --remote origin as the parameter.

Does your git remote -v command have the "https://myprivate-repo-ip:8443/git/dev-repo.git" in it? if so, what is the short name? Pass that to --remote.

Owner

miketheman commented Mar 23, 2013

I think you may be passing the wrong argument to the --remote flag.

Here's what you may see from a git remote -v run:

$ git remote -v
origin  git@github.com:miketheman/knife-community.git (fetch)
origin  git@github.com:miketheman/knife-community.git (push)

In this case, I can see that the remote name is origin, and if I wanted to pass this to knife-community, I would use --remote origin as the parameter.

Does your git remote -v command have the "https://myprivate-repo-ip:8443/git/dev-repo.git" in it? if so, what is the short name? Pass that to --remote.

@miketheman

This comment has been minimized.

Show comment
Hide comment
@miketheman

miketheman Apr 5, 2013

Owner

Hi @meenarc,

Were you able to resolve the issue? I wanted to follow up and see if everything was working out.

Owner

miketheman commented Apr 5, 2013

Hi @meenarc,

Were you able to resolve the issue? I wanted to follow up and see if everything was working out.

@ghost ghost assigned miketheman Apr 7, 2013

@meenarc

This comment has been minimized.

Show comment
Hide comment
@meenarc

meenarc Apr 9, 2013

Sorry about the delayed reply. Our internal gitblit was upgraded and couldn't try things for a bit and I also ran into ruby upgrade issues
It worked smoothly after the rets of the stuff got resolved

meenarc commented Apr 9, 2013

Sorry about the delayed reply. Our internal gitblit was upgraded and couldn't try things for a bit and I also ran into ruby upgrade issues
It worked smoothly after the rets of the stuff got resolved

@meenarc meenarc closed this Apr 9, 2013

@miketheman

This comment has been minimized.

Show comment
Hide comment
@miketheman

miketheman Apr 9, 2013

Owner

Glad to hear it!

Owner

miketheman commented Apr 9, 2013

Glad to hear it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment