Depends, the pro git book shows a few different workflows. One is to 
have a 'golden' repo and pull in from admins' checkout (like 
/home/bofh/working/git/puppet master) after it has been human code 
reviewed. That's what we do at $dayjob right now. At that point we run a 
script that runs through syntax checks of all conceivable languages 
(ERB, ruby, perl, bash, puppet) of changed files, checks for nodes in 
stored config that match more than one node regex if you've edited the 
nodes.pp, checks for duplicate class definitions, and finally compiles 
the catalog of one machine from each changed puppet class to catch 
run-time errors. After that a push to the origin/master is done.

The SVN workflow I do at another gig is totally different. You do your 
changes then run that script before you commit. It also supports a 
switch to test the diff between HEAD and what's deployed. The thing with 
git is that the commit and deploy sort of become one action... It 
doesn't have to be that way but it's kind of natural IMO.

On 04/09/2011 08:43 PM, Matthew Barr wrote:
> We're in the process of building out a puppet install.  We're also going to 
> be using git for version control.
>
> What would you consider key things to remember?  or tools to use?
>
> In SVN @ a former job, we used to have a post commit hook that sent a copy of 
> the commit to the team.
>
> So:  What do people do for git:  web front end, code review tools, anything 
> else I'm missing?
>
> Matthew
> _______________________________________________
> Discuss mailing list
> [email protected]
> https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
> This list provided by the League of Professional System Administrators
>   http://lopsa.org/


-- 
--
Joe McDonagh
Operations Engineer
AIM: YoosingYoonickz
IRC: joe-mac on freenode
"When the going gets weird, the weird turn pro."

_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to