gitolite/t/rollback.server

#!/bin/bash

cd
rm -rf .ssh .gitolite .gitolite.rc repositories gitolite-install /tmp/glrb
tar xf rollback.tar
( cd /tmp; tar xf ~/rollback2.tar )

# if arg1 is a directory, we have to overwrite sources from there (see commit
# message for details)
if [ -d "$1" ]
then
    cd .gitolite
    /bin/cp -a $1/{src,hooks} .
    cd
fi
finally, open up my secret test scripts... ...after getting rid of most of the hardcoding (though not all!) 2010-06-12 07:33:53 +02:00			`#!/bin/bash`

			`cd`
make REPO_BASE absolute early $ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as $REPO_BASE, except it is meant to be passed to hooks, ADCs and other child programs. And since you can't be sure where the child program starts in, this became an absolute path. Gradually, however, I started using it wherever I needed an absolute path (mostly in code that jumps around various directories to do stuff). Which is silly, because there's no reason $REPO_BASE cannot also be made an absolute, even if the rc file has a relative path. So that's what I did now: made $REPO_BASE absolute very early on, and then systematically changed all uses of the longer form to the shorter form when appropriate. And so the only thing we now use the longer one for is to pass to child programs. (Implementation note: The actual change is not very big, but while I was about it I decided to make the test suite able to test with an absolute REPO_BASE also, which is why the commit seems so large.) ---- This all started with a complaint from Damien Regad. He had an extremely odd setup where his bashrc changed PWD to something other than $HOME before anything else ran. This caused those two variables to beceom inconsistent, and he had a 1-line fix he wanted me to apply. I generally don't like making special fixes for for non-standard setups, and anyway all he had to do was set the full path to REPO_BASE in the rc file to get around this. Which is what I told him and he very politely left it at that. However, this did get me thinking, and I soon realised I was needlessly conflating "relative versus absolute" with "able to be passed to child programs". Fixing that solved his problem also, as a side-effect. So I guess this is all thanks to Damien! 2011-03-18 06:29:52 +01:00			`rm -rf .ssh .gitolite .gitolite.rc repositories gitolite-install /tmp/glrb`
finally, open up my secret test scripts... ...after getting rid of most of the hardcoding (though not all!) 2010-06-12 07:33:53 +02:00			`tar xf rollback.tar`
make REPO_BASE absolute early $ENV{GL_REPO_BASE_ABS} is meant to point to the same directory as $REPO_BASE, except it is meant to be passed to hooks, ADCs and other child programs. And since you can't be sure where the child program starts in, this became an absolute path. Gradually, however, I started using it wherever I needed an absolute path (mostly in code that jumps around various directories to do stuff). Which is silly, because there's no reason $REPO_BASE cannot also be made an absolute, even if the rc file has a relative path. So that's what I did now: made $REPO_BASE absolute very early on, and then systematically changed all uses of the longer form to the shorter form when appropriate. And so the only thing we now use the longer one for is to pass to child programs. (Implementation note: The actual change is not very big, but while I was about it I decided to make the test suite able to test with an absolute REPO_BASE also, which is why the commit seems so large.) ---- This all started with a complaint from Damien Regad. He had an extremely odd setup where his bashrc changed PWD to something other than $HOME before anything else ran. This caused those two variables to beceom inconsistent, and he had a 1-line fix he wanted me to apply. I generally don't like making special fixes for for non-standard setups, and anyway all he had to do was set the full path to REPO_BASE in the rc file to get around this. Which is what I told him and he very politely left it at that. However, this did get me thinking, and I soon realised I was needlessly conflating "relative versus absolute" with "able to be passed to child programs". Fixing that solved his problem also, as a side-effect. So I guess this is all thanks to Damien! 2011-03-18 06:29:52 +01:00			`( cd /tmp; tar xf ~/rollback2.tar )`
gqt -- gitolite quick (re-)test sometimes I want to quickly test a few lines of change within the context of a currently-running/just-ran test, without doing the rollback etc. Here's how you do that now: - in your source tree, make the change and then run: cp -a src hooks contrib/adc /some/tmp/place - go to the tester userid and re-run your tests like so: GQT=/some/tmp/place ./test-driver.sh it'll rollback as normal then overwrite src and hooks from $GQT Also, there's now a "dbg" sub that can be used for quick printf-style debugging. 2010-07-20 09:09:06 +02:00
			`# if arg1 is a directory, we have to overwrite sources from there (see commit`
			`# message for details)`
			`if [ -d "$1" ]`
			`then`
			`cd .gitolite`
			`/bin/cp -a $1/{src,hooks} .`
			`cd`
			`fi`