Nick Chalko wrote:
Sam,

Now that I have http://chalko.com/gump is working, I want to automate it.
Is your the cron script that you use somewehre I can take a look at it? If not can you post it here?
Each varies slightly, but here's a typical one. I've also attached the source to timeout.. a very handy utility.

export JAVA_HOME=/usr/j2sdk1.4.1_01
export PATH=/data/gump/bin:$JAVA_HOME/bin:/usr/local/bin:$PATH
export CLASSPATH=$JAVA_HOME/lib/tools.jar
export CVS_RSH=`which ssh`
export LOG=/data/gump/log/gen.html
export LD_LIBRARY_PATH=/lib:/usr/lib:/usr/local/lib

umask 002

echo \<XMP\> > $LOG
cd /home/rubys/gump
if ! /home/rubys/bin/timeout 1200 cvs update >> $LOG; then
sleep 90
echo Retrying... >> $LOG
/home/rubys/bin/timeout 1200 cvs update >> $LOG
fi
rm .timestamp
bash gen.sh -cp "/home/rubys/bin/timeout 1200" 2>&1 >> $LOG
echo >> $LOG
bash work/build.sh gump clean >> $LOG
echo >> $LOG
export >> $LOG
echo \</XMP\> >> $LOG

# /usr/X11R6/bin/Xvfb :8 &
# export DISPLAY=:8

cd /data/gump
bash update.sh all
rm /data/gump/jars/latest
bash build.sh all
pkill -P $$

Getting the latest and dated builds right can be a pain.
it is about as easy as cvs update...

- Sam Ruby

Attachment: timeout.zip
Description: Zip compressed data

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to