On 2013-03-19, at 00:52, Ben Coman <btc@openInWorld.com> wrote:
Maybe this can be arranged in a lock-step fashion. Updated VMs test against last green image. Updated image tests against last green VM.
that is sort of already happening: (still needs to upgraded to 3.0): - https://ci.inria.fr/pharo/job/Pharo-2.0-Regression-Tests/ - https://ci.inria.fr/pharo/view/VM/job/PharoVM-tests/ - https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/
Camillo Bruni wrote:
On 2013-03-18, at 07:37, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi Camillo,
Thanks for the remarks.
We (or at least I :)) want to use the latest of everything :). Moose switched to developing on bleeding edge about 7 years ago, and the only thing that still remained fixed was the VM.
Now, we work with the latest VM and like that we can check integration and give feedback. I guess this is particularly important now that you chose Moose to be one of the benchmarks for the VM stability.
If it will really not work, we will use the stable one, but at the moment, it works :)
ok, so you are fully aware ;), indeed that will help us certainly to find bugs in the VM!
Cheers, Doru
On Mar 17, 2013, at 11:20 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
Nice! good to see ;)
Some little remarks:
- `wget --quiet -qO` can be simplified as `wget --quiet -O -` since -q is just the short form for --quiet ;) - I would not use the ciPharoVMLatest.sh but ciPharoVM.sh since Latest might break unexpectedly whereas ciPharoVM.sh points to latest stable release
best cami
On 2013-03-17, at 22:02, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: http://www.tudorgirba.com/blog/moose-4-8-on-jenkins
Cheers, Doru
-- www.tudorgirba.com
"Be rather willing to give than demanding to get."
-- www.tudorgirba.com
"Reasonable is what we are accustomed with."