gitolite/hooks/gitolite-admin/post-update

#!/bin/sh

# 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
    }

# checkout the master branch to $GL_ADMINDIR
# (the GL_ADMINDIR env var would have been set by gl-auth-command)
GIT_WORK_TREE=$GL_ADMINDIR git checkout -f master

od=$PWD
cd $GL_ADMINDIR
$GL_BINDIR/gl-compile-conf

cd $od

ADMIN_POST_UPDATE_CHAINS_TO=` cd;perl -e 'do ".gitolite.rc"; print $ADMIN_POST_UPDATE_CHAINS_TO'`
[ -n "$ADMIN_POST_UPDATE_CHAINS_TO" ] || ADMIN_POST_UPDATE_CHAINS_TO=hooks/post-update.secondary

if [ -f $ADMIN_POST_UPDATE_CHAINS_TO ] || [ -L $ADMIN_POST_UPDATE_CHAINS_TO ]
then
    exec $ADMIN_POST_UPDATE_CHAINS_TO "$@"
fi
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 19:53:52 +02:00			`#!/bin/sh`

(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 15:31:05 +02:00			`# 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 09:47:02 +02:00			`# 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 08:05:48 +01:00			`# (the GL_ADMINDIR env var would have been set by gl-auth-command)`
(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 15:31:05 +02:00			`GIT_WORK_TREE=$GL_ADMINDIR git checkout -f 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 09:47:02 +02:00
we're getting a nice solaris workout after a long time :) 2010-03-30 14:23:40 +02:00			`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 09:47:02 +02:00			`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 08:05:48 +01:00			`$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 14:56:26 +01:00
we're getting a nice solaris workout after a long time :) 2010-03-30 14:23:40 +02:00			`cd $od`
minor oopsie in post-update hook chaining 2010-03-17 16:06:51 +01:00
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 14:56:34 +02:00			ADMIN_POST_UPDATE_CHAINS_TO=` cd;perl -e 'do ".gitolite.rc"; print $ADMIN_POST_UPDATE_CHAINS_TO'`
			`[ -n "$ADMIN_POST_UPDATE_CHAINS_TO" ] \|\| ADMIN_POST_UPDATE_CHAINS_TO=hooks/post-update.secondary`

			`if [ -f $ADMIN_POST_UPDATE_CHAINS_TO ] \|\| [ -L $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 14:56:26 +01:00			`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 14:56:34 +02:00			`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 14:56:26 +01:00			`fi`