deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

logging (but see below)

Browse source 
The logging is both for paranoia and parsing/automated processing.  The
ones you're probably interested in parsing should be easy to pick out
and are very likely to have tab-delimited fields already.
This commit is contained in:
Sitaram Chamarty 2012-03-17 21:13:28 +05:30
parent 5b93dd4b53
commit 44e6bc4bb2
8 changed files with 80 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

3
src/Gitolite/Hooks/Update.pm
View file

@ -20,15 +20,18 @@ use warnings;
sub update {
trace( 2, @ARGV );
gl_log( 'update', @ARGV );
# this is the *real* update hook for gitolite
my ( $ref, $oldsha, $newsha, $oldtree, $newtree, $aa ) = args(@ARGV);
my $ret = access( $ENV{GL_REPO}, $ENV{GL_USER}, $aa, $ref );
trace( 1, "access($ENV{GL_REPO}, $ENV{GL_USER}, $aa, $ref)", "-> $ret" );
gl_log( 'update:check', $ENV{GL_REPO}, $ENV{GL_USER}, $aa, $ref, '->', $ret );
_die $ret if $ret =~ /DENIED/;
check_vrefs( $ref, $oldsha, $newsha, $oldtree, $newtree, $aa );
gl_log( 'update:OK', $ENV{GL_REPO}, $ENV{GL_USER}, $aa, @ARGV );
exit 0;
}