To clarify I can explain again what I already sent the 23. Oct: > On 23 Oct 2012, at 00:28, Camillo Bruni <[email protected]> wrote: >> I finally managed to create a zero conf pharo image build setup: >> >> # =========================================================================== >> curl http://pharo.gforge.inria.fr/ci/ciPharo20Cog.sh | bash => has been replaced by wget since I did not manage to install curl under windows => wget --quiet -qO - http://pharo.gforge.inria.fr/ci/script/ciPharo20Cog.sh | bash => downloads the latest Pharo20 image and latest Cog Build from - http://pharo.gforge.inria.fr/ci/image/20 - http://pharo.gforge.inria.fr/ci/vm/cog/
>> ./vm.sh Pharo.image save $JOB_NAME --delete-old => renames the image, you can easily do: ./vm.sh Pharo.image save --help >> REPO=http://smalltalkhub.com/mc/dh83/nabujito/main >> ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfNabujito >> --install=development => self explaining, again you can see the help >> ./vm.sh $JOB_NAME.image test --junit-xml-output "Nabujito.*" => runs all tests in the Nabujito and subpackages, furthermore outputs jenkins readable test xmls >> zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes >> # =========================================================================== >> >> ./ciPharo20Cog.sh --help >> >> This is an entry point script for any Pharo image CI >> This script will download the latest Pharo 2.0 image and the latest VM >> >> Result in the current directory: >> vm directory containing the VM >> vm.sh script forwarding to the VM inside vm/ >> Pharo.image The latest pharo image >> Pharo.changes The corresponding pharo changes" >> >> # =========================================================================== see? properly documented... I do not see how this could have gone past you..
