When pushing from work do you push to non-work repositories using your work key?
On 8 March 2013 17:15, Benson Margulies <[email protected]> wrote: > As always, explaining the actual problem I'm trying to solve may help. > > I need to maintain two identities on github: one for work, and one for > not-so-work. So, I have two ssh key pairs. > > Using git from command line, I address this with an option to git when I > clone: > > git clone --config ssh.key=/users/benson/.ssh/id_basis_rsa "$@" > > Thus, the clone learns the ssh.key location, and everybody is happy. > > So, I'd like to be able to put "--config > ssh.key=/users/benson/.ssh/id_basis_rsa" into settings.xml, and have the > release plugin use it for :perform. One approach would be to add hair to > the SCM plugin to have the git-config.xml (I've probably misquoted the > name) contain, essentially, a map from scm URLs to options, so that, in > that file, I could declare the git repos that need to use the alternative > key. > > > > On Fri, Mar 8, 2013 at 8:59 AM, Robert Scholte <[email protected]> > wrote: > > > Please check GitCheckoutCommand[1] > > > > Robert > > > > [1] http://maven.apache.org/scm/**maven-scm-providers/maven-scm-** > > providers-git/maven-scm-**provider-gitexe/xref/org/** > > apache/maven/scm/provider/git/**gitexe/command/checkout/** > > GitCheckOutCommand.html< > http://maven.apache.org/scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/xref/org/apache/maven/scm/provider/git/gitexe/command/checkout/GitCheckOutCommand.html > > > > > > > > Op Fri, 08 Mar 2013 14:33:16 +0100 schreef Brett Porter < > [email protected] > > >: > > > > > > > >> On 08/03/2013, at 11:59 PM, Benson Margulies <[email protected]> > >> wrote: > >> > >> I'd like to add some 'clone' options for use with git in > >>> release:perform that could live in settings.xml. > >>> > >> > >> I'm curious - how would clone options look in settings.xml? Aside from > >> properties, or perhaps server credentials - most other things go into > >> plugin configuration. > >> > >> I'm not even sure how > >>> many JIRAs I need. Is this something that gets done in the scm plugin > >>> and then cross-wired to the release plugin? > >>> > >> > >> I believe it is what you meant, but for clarity the SCM library supports > >> the SCM plugin (part of the SCM subproject) and the Release plugin. I > would > >> start at the release plugin, and propose changes to the SCM API as > needed > >> (as it may have capabilities already that are just not exposed in the > way > >> you want). The SCM API knows nothing about Maven or the settings.xml > file, > >> so anything you want to configure will get passed in via the release > plugin. > >> > >> What are you looking at working on? > >> > >> - Brett > >> > >> -- > >> Brett Porter > >> [email protected] > >> http://brettporter.wordpress.**com/ <http://brettporter.wordpress.com/> > >> http://au.linkedin.com/in/**brettporter< > http://au.linkedin.com/in/brettporter> > >> http://twitter.com/brettporter > >> > >> > >> > >> > >> > >> > >> > ------------------------------**------------------------------**--------- > >> To unsubscribe, e-mail: [email protected].**org< > [email protected]> > >> For additional commands, e-mail: [email protected] > >> > > > > ------------------------------**------------------------------**--------- > > To unsubscribe, e-mail: [email protected].**org< > [email protected]> > > For additional commands, e-mail: [email protected] > > > > >
