On 5 February 2013 15:12, Camillo Bruni <[email protected]> wrote: > 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..
it did. It was because we didn't had time to catch-up since argentina trip. up until you came back at january. you, of course, can explain it as my lazyness or whatever.. but the fact is that i have no idea what you did.. and how to use it. having a documentation, is not the same as seeing the whole picture. i want to understand, how it works and why it works like that, not how to use it. like following: ciCog.sh ciCogVM.sh ciNBCog.sh ciNBCogVM.sh ciPharo13.sh ciPharo14.sh ciPharo14Cog.sh ciPharo14CogVM.sh ciPharo20.sh ciPharo20Cog.sh ciPharo20CogVM.sh ciPharo20NBCog.sh ciPharo20NBCogVM.sh ciPharo20PharoVM.sh ciPharo20Rizel.sh ciPharo20RizelVM.sh ciPharoVM.sh ciRizel.sh ciRizelVM.sh this list burns my eyes. and having same problem,as Marcus asks about VMs: which one i have to use? Is there a way to have less? just wonder. -- Best regards, Igor Stasenko.
