Hi Pavel, Yes, I did some experiments to use the latest compiled (and successfully tested) VM for Jenkins jobs. I choose the following option to avoid too much additional configuration to jenkins jobs : The build.sh script is used in most of jobs defined in jenkins. This script use the PHARO_VM environment variable to get the VM path. What I did is that is the variable is not defined, it calls a script named fetchLatestVM.sh to download the appropriate VM (according to OS @ Architecture)in the job workspace. Then, the PHARO_VM is set with the downloaded VM.
I was not aware of other jobs that don't use the build.sh script. I will update the build-kernel.sh script to have the same behavior as build.sh. I will also update the job. Thank for your feedback. Regards, Christophe. Le 10 mai 2012 à 14:22, Pavel Krivanek a écrit : > Hi, > > I got this error on Pharo Kernel 2.0 Jenkins build: > PHARO_VM environment variable is not set. > > Did somebody some VM related changes on Jenkins? > > -- Pavel >
