On Tue, Jul 12, 2011 at 2:34 PM, Igor Stasenko <[email protected]> wrote: > On 12 July 2011 10:58, Pavel Krivanek <[email protected]> wrote: >> Igor, >> >> please publish then server versions of build scripts like build13.sh, > > build.sh on git is based on build13.sh. The old build.sh was different > in a way how it handles image stalls. > There was loop waiting for output from image. And if nothing happens > it kills VM process. > Now since in 1.3 this is much less likely to happen (because it using > non-interactive ui manager), > we removed that. > >> build-kernel.sh etc. too. >> > it almost the same as build.sh.. but there are some difference. i > started to examine it yesterday but > then came home :)
I wrote it so I know how it differs ;-) I only want to see the current version used on server and make it available to others -- Pavel >> -- Pavel >> >> On Mon, Jul 11, 2011 at 7:47 PM, Igor Stasenko <[email protected]> wrote: >>> On 11 July 2011 19:33, Mariano Martinez Peck <[email protected]> wrote: >>>> What I great change. I think I have asked Marcus about them like 10 times >>>> :) >>> >>> So, i think you asked for a reason? :) >>> Because now you have commit rights to this repository, nothing >>> prevents you from doing what you wanted to do :) >>> >>> The changes are quite simple: >>> - avoid using absolute paths (instead use $WORKSPACE) environment variable >>> all scripts are starting from: >>> >>> if [ -z "$WORKSPACE" ] ; then >>> WORKSPACE=`pwd` >>> fi >>> >>> so, you can run them on your local machine, and they will work same on >>> server. >>> Of course if you don't make stupid mistakes... ( bah it's so easy to >>> look like an idiot with these bash scripts. I have bash/sh !!!) >>> >>> When you need to invoke VM , use PHARO_VM environment variable. Which >>> is set on slave to point to VM. >>> Like: >>> exec "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT" -headless >>> >>> Of course, for testing freshly built VMs it may point to another >>> place, but scripts will remain same. >>> >>> (tomorrow i will start migrating VM jobs from hudson to jenkins) >>> Jenkins is more appeal and seems to be less buggy. :) >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >>> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > >
