You can use this: wget --quiet -O - get.pharo.org/$PHARO+$VM | bash
at the beginng of your script to get the latest image and VM. With that you will have a spur image and a spur vm. And at the end: rm *.image *.changes rm -rf pharo-vm If there is still a problem I think it is a bug in Pharo with the migration. On Thu, Dec 17, 2015 at 3:54 PM, Johan Fabry <jfa...@dcc.uchile.cl> wrote: > > Guys, how should I adapt my CI job ? > >> On Dec 15, 2015, at 12:25, Johan Fabry <jfa...@dcc.uchile.cl> wrote: >> >> >> Sorry for the stupid question, but how should I adapt my CI job? I saw that >> the last build failed with no tests being run, so I guess this was due to >> the VM being changed. >> >>> On Dec 14, 2015, at 07:24, Esteban Lorenzano <esteba...@gmail.com> wrote: >>> >>> 5) You will need to adapt your Pharo 5.0 related apps and CI processes (to >>> take care about new VM). >> >> >> >> ---> Save our in-boxes! http://emailcharter.org <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry >> PLEIAD and RyCh labs - Computer Science Department (DCC) - University of >> Chile >> >> >> > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of > Chile > > -- Cheers Cyril Ferlicot
