moose job on jenkins
Locked
 
|
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." |
|
|
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 <[hidden email]> 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." > > > > |
|
|
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 :) Cheers, Doru On Mar 17, 2013, at 11:20 PM, Camillo Bruni <[hidden email]> 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 <[hidden email]> 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." |
|
|
Hi Camillo,
Something happened with the execution rights of the scripts because in the meantime: wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh | bash wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharoLatestVM.sh | bash do not have execution rights. Cheers, Doru On Mar 18, 2013, at 7:37 AM, Tudor Girba <[hidden email]> 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 :) > > Cheers, > Doru > > > On Mar 17, 2013, at 11:20 PM, Camillo Bruni <[hidden email]> 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 <[hidden email]> 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." > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower." |
|
|
Never mind. My bad.
Doru On Mar 18, 2013, at 8:26 AM, Tudor Girba <[hidden email]> wrote: > Hi Camillo, > > Something happened with the execution rights of the scripts because in the meantime: > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh | bash > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharoLatestVM.sh | bash > > do not have execution rights. > > Cheers, > Doru > > > On Mar 18, 2013, at 7:37 AM, Tudor Girba <[hidden email]> 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 :) >> >> Cheers, >> Doru >> >> >> On Mar 17, 2013, at 11:20 PM, Camillo Bruni <[hidden email]> 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 <[hidden email]> 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." >> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut." |
|
|
In reply to this post by Tudor Girba-2
Doru in your blog you did not mention if you added the tag on the class side of the handler.
I have the impression that you have to. May be I could use your blog as an example for the zeroConfig chapter. Stef On Mar 18, 2013, at 8:26 AM, Tudor Girba <[hidden email]> wrote: > Hi Camillo, > > Something happened with the execution rights of the scripts because in the meantime: > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh | bash > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharoLatestVM.sh | bash > > do not have execution rights. > > Cheers, > Doru > > > On Mar 18, 2013, at 7:37 AM, Tudor Girba <[hidden email]> 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 :) >> >> Cheers, >> Doru >> >> >> On Mar 17, 2013, at 11:20 PM, Camillo Bruni <[hidden email]> 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 <[hidden email]> 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." >> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > > |
|
|
Hi, You only should add the tag on the class side if you want to have a shortcut for the command. Indeed, I added these short names on the class side for our commands.
Cheers, Doru On Mon, Mar 18, 2013 at 9:10 AM, stephane ducasse <[hidden email]> wrote: Doru in your blog you did not mention if you added the tag on the class side of the handler. "Every thing has its own flow"
|
|
|
In reply to this post by Tudor Girba-2
On 2013-03-18, at 07:37, Tudor Girba <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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." > > |
|
|
Maybe this can be arranged in a lock-step fashion.
Updated VMs test against last green image. Updated image tests against last green VM. cheers -ben Camillo Bruni wrote: > On 2013-03-18, at 07:37, Tudor Girba <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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." >> >> >> > > > > |
|
|
On 2013-03-19, at 00:52, Ben Coman <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]> 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." >>> >>> >>> >> >> >> >> > > |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |