[Pharo-users] Pillar for 30 gone the way of the dodo on the CI

Peter Uhnak i.uhnak at gmail.com
Thu Oct 1 04:05:24 EDT 2015

In Jenkins you specify configuration matrix (versions of pharo versus type (development, stable, ...)).. So it will run development for all versions, even pharo 30 (which is now permanently broken)

-----Original Message-----
From: "Stephan Eggermont" <stephan at stack.nl>
Sent: ‎10/‎1/‎2015 9:47 AM
To: "pharo-users at lists.pharo.org" <pharo-users at lists.pharo.org>
Subject: Re: [Pharo-users] Pillar for 30 gone the way of the dodo on the CI

On 01-10-15 09:41, Stephan Eggermont wrote:
> On 30-09-15 19:57, Ferlicot D. Cyril wrote:
>> We removed the Pillar job for Pharo 3 because we introduced an new
>> feature not backward compatible.
> Why is that a reason to remove the build? You have a configuration,
> don't you?

I would suggest: move to a separate job that is run much less often
and doesn't keep so many old artifacts. That makes it easier to get old 
stuff running again.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20151001/6ae17327/attachment.html>

More information about the Pharo-users mailing list