On Fri, May 08, 2009 at 03:43:30PM -0400, Mark Plaksin wrote:
> What's the best way to make the update hook do a syntax check?
>
> We want to switch our Puppet [1] config repository from SVN to Git. Our
> SVN repository has a pre-commit hook that does a syntax check. The hook
> runs Puppet to check the syntax of the file(s) being committed and if the
> check fails, the commit fails. With SVN that hook runs on the server so
> it's easy to have (the correct version of) the puppet binary there for
> the hook to use.
>
> Once Puppet config changes are committed to to our SVN repository they
> are automatically pushed into our production Puppet config. We want to
> do something similar with Git--once commits are successfully pushed to
> the master repository they are automatically pulled and become our
> production Puppet config.
That sounds like a reasonable goal. In the hook itself, you can do one
of:
1. Look at the diff to the original version to make sure you're not
introducing anything bogus. This is sufficient for syntax issues on
single lines, etc, and is obviously pretty efficient. But it won't
cover "does this whole thing build?" types of checks, which I think
is what you want.
2. Check out the whole tree to a temp directory and run your full
syntax check there. The simplest way would be by using "git
archive" to generate the tree. You can make this a bit more
efficient by keeping the temp directory between runs and using
git to just update the changed files. Off the top of my head, that
would look something like:
$ cat <<EOF >.git/hooks/update
#!/bin/sh
GIT_INDEX_FILE=/path/to/tempdir/index; export GIT_INDEX_FILE
cd /path/to/tempdir/tree &&
mkdir -p tree &&
git read-tree "$3" &&
git checkout-index &&
your_syntax_check
EOF
$ chmod +x .git/hooks/update
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html