Why don't just build two targets, one for a latestVersion and other for baseline. And mark the two builds differently. That the machine realize the hard work. That is the reason for them.
El mar, 18-01-2011 a las 21:14 +0100, Mariano Martinez Peck escribió: > Hi. A trade-off here. Right now, the PharoDev image from Hudson is > being built using ConfigurationOfPharo project lastestVersion. > This is more or less good because we have the last version of the > ConfigurationOfPharo. But at the same time, updating the versions of > ConfigurationOfPharo is tedious. So, what about loading the baseline > istead? So that metacello automatically load the latest version of > each package/project ? > The good thing is that every change in external > configurations/packages will be automatically included. But at the > same time this is a disavtange because we can build crap (someone > commits something that doesn't work). When updating > ConfigurationOfPharo by hand we usually test it before.... > > anyway, isn't this the idea if hudson? if it builds crap, we want to > know it, as soon as possible. NOBODY should use a Hudson image (as it > is now) for a stable Pharo1.2 image. > > what do you think? > > cheers > > mariano -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx
