25 Sep
2015
25 Sep
'15
2:19 p.m.
On 25 Sep 2015, at 14:08, Andrei Chis
<chisvasileandrei(a)gmail.com> wrote:
https://ci.inria.fr/moose/view/Moose%205.1/job/roassal2-pharo4/
CI job that loads roassal2 #stable on Pharo 4.
Cool !
Cheers,
Andrei
On Fri, Sep 25, 2015 at 1:10 PM, Peter Uhnák <i.uhnak(a)gmail.com> wrote:
On Fri, Sep 25, 2015 at 12:34 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
On 25 Sep 2015, at 12:08, Peter Uhnák
<i.uhnak(a)gmail.com> wrote:
There should be CI job for Roassal2 #stable and Pharo4.
Especially if most of Roassal contributors/devs are in Pharo 5 and thus only end-users
will notice it.
(with the multi-configuration job in Jenkins it's easy to setup custom matrix)
Yes, this is so useful, I can hardly imagine doing it without a CI (no one has time to do
all the testing)
https://ci.inria.fr/pharo-contribution/job/ZincHTTPComponents/
The cool thing is that there are also images as artefacts, which users can download when
they have trouble building from source.
But there have to be project specific tests as well.
Roassal of course does have CI (just like the rest of the Moose), but it tests Pharo 5.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev