Yet another time, the truth tells me DON'T USE BASH... Or I just know too little "$*" vs "$@" did the job...
On 2012-11-02, at 09:17, Pavel Krivanek <[email protected]> wrote: > It works now well. Thanks. > > -- Pavel > > On Thu, Nov 1, 2012 at 11:37 PM, Camillo Bruni <[email protected]> wrote: >> I tried to fix the script AFAIK it work locally. >> can you retry the stuff on the server? >> >> best >> cami >> >> On 2012-11-01, at 22:56, Camillo Bruni <[email protected]> wrote: >>> maybe we should change vm.sh? >>> I'll have a look at it. >>> >>> >>> On 2012-11-01, at 17:15, Pavel Krivanek <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> in a Jenkins job configuration I have this bash line for Pharo start: >>>> >>>> ./vm.sh "images/$IMAGE_NAME.image" "$WORKSPACE/support/pharo.tank" >>>> "$WORKSPACE/support/pharo.tankst" >>>> >>>> In the console I got this error >>>> >>>> + ./vm.sh images/PharoKernelTanker-2.0.image >>>> '/builds/jenkins/workspace/Pharo Kernel 2.0 Reload by >>>> Fuel/support/pharo.tank' '/builds/jenkins/workspace/Pharo Kernel 2.0 >>>> Reload by Fuel/support/pharo.tankst' >>>> ==== Startup Error: FileDoesNotExist: >>>> file:///builds/jenkins/workspace/Pharo Kernel 2.0 Reload by >>>> Fuel/images/Fuel/support/pharo.tank >>>> >>>> As you may see, the image argument is passed by full path but it is >>>> interpreted wrongly. Tanker uses simply 'xxx' asFileReference on >>>> argument. >>>> The problem is clearly in the spaces in the path (see >>>> "Fuel/support/pharo.tank" at the end of path). On my localmachine id >>>> fails too if I use "$PWD/pharo.tank" "$PWD/pharo.tankst" as argument >>>> and the path does contain spaces. When I have this files in the image >>>> directory (even when the image path contains spaces) and I use only >>>> names of this files without full path, they are loaded well. >>>> >>>> Cheers, >>>> -- Pavel >>>> >>> >> >> >
