I was looking in the image/ folder with the newImage.sh script as I wanted to understand what was happening in there. So, this requires something like $PHAROVM to exist and be set to something proper (added to my .profile) Then, there is still ci.lille... in there, to be removed. Next, I wanted to make sense of the script itself. I commented out the part where the pregenerated image got downloaded as I wanted to see things work from zero and not merely a prebuilt image. So, I commented out the prebuilt part. # ---------------------------------------------------------------------------- # echo -e "${YELLOW}LOADING PREBUILT IMAGE" $NO_COLOR # echo " $PREBUILT_IMAGE_URL" # wget $WGET_CERTCHECK "$PREBUILT_IMAGE_URL" --output-document="image.zip" && \ # unzip image.zip && \ # rm image.zip && \ # openImage "$PWD/generator.image" "$PWD/ImageConfiguration.st" && exit 1 And then, I got: [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspacePharoVMFebruary2013/buildarea/cog/image philippeback$] ./newImage.sh FETCHING FRESH IMAGE https://ci.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifact/Pharo... --2013-02-16 14:10:11-- https://ci.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifact/Pharo... Which failed. The right URL is: URL="https://ci.inria.fr/pharo/view/Pharo-1.4/job/Pharo-1.4/lastSuccessfulBuild/a..." Also, it seems that the original contents of PharoVM do not contain the .sources, and this generates a UI message one has to click, which is annoying. Phil 2013/2/16 Ben Coman <btc@openinworld.com>:
Marcus Denker wrote:
On Feb 15, 2013, at 6:26 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Hi,
Finally, with a lot of work, mana, power cards and jedi tricks, we made the pharo vm builds work again :)
This builds are up-to-date with latest sources from Eliot's cog and adds pharo branding (AFAIK, this is the first time we are going to release something like that :)
You can download it here: https://ci.inria.fr/pharo/view/VM/job/PharoVM/
Very good!
So now we need to step by step.. -> use the build in the one-click -> link the VM zips on pharo-project.org -> replace the VM we use for running jobs on jenkins with this.
And of course: -> test those builds on all three architectures automatically with a test image (e.g. current 2.0 with all failing tests removed) The idea is that this image should not change frequently (the only variable is the VM)
Could the CI test new VMs against all previous "release" images eg Pharo 1.3, 1.4, 1.4 Summer, 2.0, 2.x or some subset, like the last release of each major version. While you may not want a very old release to fail a VM, at least the compatibility would be on record.
-> only when this is green the zip is updated in the archive