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@stack.nl> Sent: â10/â1/â2015 9:47 AM To: "pharo-users@lists.pharo.org" <pharo-users@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. Stephan