deac/gitolite
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
gitolite/hooks/gitolite-admin/post-update

35 lines
1.1 KiB
Text
Raw Permalink Normal View History

p-t-a: make the post-update hook a separate file... ...and just refer to it in the doc. This hook will acquire more code soon, when we do delegations :)
2009-10-02 23:23:52 +05:30
#!/bin/sh
It's official now; Solaris sh is brain dead... For example, this program #!/bin/sh die() { echo die called with $1; exit 1; } >&2 die foo die bar will print *both* those messages! I honestly don't care if this is posix or not, but it is BRAIN DEAD for the ">&2" to change the meaning from {} to () Oh and the grep thing is even worse. echo foo | grep ^/ works fine in an interactive shell but in a script it attempts to *execute* "/", complains, while simultaneously complaining about usage of grep. It's almost like it's treating ^ like |
2011-10-20 15:40:17 +05:30
die() { echo "$@" >&2; exit 1; }
die() needs to be defined in post-update hook (and in one other place it needs to be defined earlier) I never caught this because in my testing those error conditions -- caused by lack of afc3a06 -- never came up.
2011-06-19 06:54:52 +05:30
gitolite v2.0rc1 -- please see new developer-notes doc
2011-01-15 21:09:56 +05:30
[ -z "$GL_RC" ] && die "ENV GL_RC not set"
[ -z "$GL_BINDIR" ] && die "ENV GL_BINDIR not set"
[ -z "$GL_ADMINDIR" ] && die "ENV GL_ADMINDIR not set"
(security) a different fix in place of 5fd9328 SECURITY NOTE: if you deleted or renamed a pubkey file after 5fd9328 went in (April 12th), please: - upgrade asap, then - go to your latest gitolite-admin clone and "git push -f" Otherwise this is not urgent. 5fd9328 (and its minor successor 813a2a9) were about preventing the gitolite admin from sneaking in files to src/ and hooks/ into $GL_ADMINDIR. It seemed easy enough to do this by converting the path-less checkout to a with-paths checkout, but this has caused a worse problem -- deleting a keydir/foo.pub now no longer has an effect; the file still hangs around in the work tree. Ouch! (and thanks to teukka for noticing) We now do this check as a separate step, so the checkout can revert to being path-less.
2010-04-20 19:01:05 +05:30
# ensure that the admin is not sneaking in src/ and hooks/ :)
GIT_WORK_TREE=$GL_ADMINDIR git ls-tree --name-only master |
perl -lne 'exit 1 if /^(src|hooks)$/' || {
echo "*** ERROR ***" >&2
echo "no files/dirs called 'src' or 'hooks' are allowed, sorry" >&2
echo "until those files are deleted, the post-update hook will not run" >&2
exit 1
}
pta-hook.sh: collect delegated config fragments collect the delegated config fragments from correspondingly named branches of the gitolite-admin repo, and put them all in conf/fragments/ also deprecate changes to conf and keydir locations from now on
2009-10-03 13:17:02 +05:30
# checkout the master branch to $GL_ADMINDIR
auth/install/pu-hook: pass ADMINDIR and BINDIR via ENV The admin repo's post-update hook needs to know where $GL_ADMINDIR is, and we had a weird way of doing that which depended on gl-install actually munging the hook code. We also always assumed the binaries are in GL_ADMINDIR/src. We now use an env var to pass both these values. This removes the weird dependency on gl-install that the post-update hook had, as well as make running other programs easier due to the new $GL_BINDIR env var.
2009-12-15 12:35:48 +05:30
# (the GL_ADMINDIR env var would have been set by gl-auth-command)
post-update learns to be quieter apparently people run it from cron, so this causes a silly one-line email saying just "Already on master" thanks to shruggar on #git for pointing out to me that it is quite safe to use --quiet and will not lose any actual error messages :)
2011-01-29 06:16:13 +05:30
GIT_WORK_TREE=$GL_ADMINDIR git checkout -f --quiet master
pta-hook.sh: collect delegated config fragments collect the delegated config fragments from correspondingly named branches of the gitolite-admin repo, and put them all in conf/fragments/ also deprecate changes to conf and keydir locations from now on
2009-10-03 13:17:02 +05:30
we're getting a nice solaris workout after a long time :)
2010-03-30 17:53:40 +05:30
od=$PWD
pta-hook.sh: collect delegated config fragments collect the delegated config fragments from correspondingly named branches of the gitolite-admin repo, and put them all in conf/fragments/ also deprecate changes to conf and keydir locations from now on
2009-10-03 13:17:02 +05:30
cd $GL_ADMINDIR
auth/install/pu-hook: pass ADMINDIR and BINDIR via ENV The admin repo's post-update hook needs to know where $GL_ADMINDIR is, and we had a weird way of doing that which depended on gl-install actually munging the hook code. We also always assumed the binaries are in GL_ADMINDIR/src. We now use an env var to pass both these values. This removes the weird dependency on gl-install that the post-update hook had, as well as make running other programs easier due to the new $GL_BINDIR env var.
2009-12-15 12:35:48 +05:30
$GL_BINDIR/gl-compile-conf
post-update hook now chains to post-update.secondary undocumented but analogous to the documented update hook chaining
2010-03-16 19:26:26 +05:30
we're getting a nice solaris workout after a long time :)
2010-03-30 17:53:40 +05:30
cd $od
minor oopsie in post-update hook chaining
2010-03-17 20:36:51 +05:30
gitolite v2.0rc1 -- please see new developer-notes doc
2011-01-15 21:09:56 +05:30
ADMIN_POST_UPDATE_CHAINS_TO=`$GL_BINDIR/gl-query-rc ADMIN_POST_UPDATE_CHAINS_TO`
allow user to define filenames that our hooks chain to (although the defaults are still update.secondary and post-update.secondary if you don't do anything)
2010-04-13 18:26:34 +05:30
[ -n "$ADMIN_POST_UPDATE_CHAINS_TO" ] || ADMIN_POST_UPDATE_CHAINS_TO=hooks/post-update.secondary
oopsies... should be checking for "-x" not just "-f or -l" to chain a hook it was trying to execute a broken symlink! (Thanks to Jeff of KDE for catching this)
2011-05-28 20:26:55 +05:30
if [ -x $ADMIN_POST_UPDATE_CHAINS_TO ]
post-update hook now chains to post-update.secondary undocumented but analogous to the documented update hook chaining
2010-03-16 19:26:26 +05:30
then
allow user to define filenames that our hooks chain to (although the defaults are still update.secondary and post-update.secondary if you don't do anything)
2010-04-13 18:26:34 +05:30
exec $ADMIN_POST_UPDATE_CHAINS_TO "$@"
post-update hook now chains to post-update.secondary undocumented but analogous to the documented update hook chaining
2010-03-16 19:26:26 +05:30
fi
Reference in a new issue Copy permalink