On 12/05/12 05:37, Konstantin Khomoutov wrote: > On Tue, 4 Dec 2012 10:43:32 -0800 (PST) > Jeffrey Marans <jmarans-re5jqeeqqe8avxtiumw...@public.gmane.org> wrote: > >> I'm working on transitioning about 15 CVS modules to GIT repositories >> and I think I've got a handle on how to translate the cvs triggers to >> make them run on the git origin. >> >> I have to create triggers that run from the bugzilla server against >> the git origin server that will branch from either main or a release >> branch to a bug branch. > > Could you please try to re-explain your idea without mentioning > Subversion and CVS completely? > > Do I understand you correctly that your bugzilla server is on a > different machine from that one hosting a central Git repository > (what you call "the origin server"), and you want actions done in > bugzilla to modify the Git repository hosted on that another machine?
I think "cvs triggers" translate as "git hooks", places to script actions on the "bugzilla server"/origin machine to perform actions upon various events such as commiting/receiving updates. To the OP, these are documented at git help hooks or man githooks Your "bugzilla server"/origin repo should have a hooks/ directory in it with sample scripts you can use as a foundation for your own scripts. > If your "Git origin server" can be accessed via SSH, you can > perform any sugrery on the remote repository using nothing but > the SSH client on the bugzilla side as SSH is a *shell.* Just as a side note, some administrators may lock down the shell used depending on the type of account login. In particular, I've got some client-facing logins on one box that use "rssh" as the login shell, limiting the users to just scp/sftp access without the ability to execute arbitrary commands (such as git). That said, the *normal* thing to do is have full ssh shell access. -tkc --