> On 25 Sep 2015, at 12:08, Peter Uhnák <i.uhnak@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.