On 2012-11-14, at 14:32, Pavel Krivanek <[email protected]> wrote:
> Hi, > > we need to modify (or create new) > http://pharo.gforge.inria.fr/ci/ciPharo20.sh and related scripts to > use the new infrastructure. Has someone rights and time to do that? the ci*.sh are already self contained and only download stuff from the files statically served under http://pharo.gforge.inria.fr/ci/* so the scripts should be fine and contain no references to the build server. So the infrastructure (will go) goes like this (comments and improvements welcome!) http://ci.inria.fr/pharo - Pharo.image => push results to http://pharo.gforge.inria.fr/ci/image/ - CogVM / NBCogVM => push results http://pharo.gforge.inria.fr/ci/vm/ all other build scripts should be in the form: ---------------------------------------------------------------------------------- wget --quiet -qO - http://pharo.gforge.inria.fr/ci/ciPharo20Cog.sh | sh ./vm.sh Pharo.image save $JOB_NAME --delete-old REPO=http://smalltalkhub.com/mc/dh83/nabujito/main ./vm.sh $JOB_NAME.image config $REPO ConfigurationOfNabujito --install=development ./vm.sh $JOB_NAME.image test --junit-xml-output "Nabujito-.*" zip -r $JOB_NAME.zip $JOB_NAME.image $JOB_NAME.changes ---------------------------------------------------------------------------------- GOAL: - 1 single bash scripts with contents similar to the example above - No additional build.sh / install.st scripts - No more Jenkins dependencies (copy scripts, getting VM, getting Image) - Always use the latest VMs / Images provided through http://pharo.gforge.inria.fr/ci/ciPharo20Cog.sh and Co best cami
