On 12/08/2010 09:09 AM, Yanni Chiu wrote:
On 08/12/10 6:48 AM, Marcus Denker wrote:
On Dec 8, 2010, at 10:25 AM, Marcus Denker wrote:
On Dec 7, 2010, at 8:42 PM, Guillermo Polito wrote:
Gofer it squeaksource: 'MetacelloRepository';
package: 'ConfigurationOfPharo';
load.
(ConfigurationOfPharo project version: '1.2-beta2') load.
Can Hudson help us in building Dev images?
Yes, will set up a build for 1.2 today.
I have set one up that takes 1.2 core, runs updates and then tries to
build dev
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/
It is failing right now.
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/2/console
This build would flag changes to PharoCore-1.2 that break Pharo(Dev)
1.2-beta2. But those core changes may be legitimate, and the fix needs
to be done in Pharo(Dev).
Maybe there should be a second build for Pharo(Dev) 1.2-baseline. The
trigger ought to be any change to a package included in the baseline,
but that seems difficult to determine. So, maybe once a day, as well as
triggering on a change to ConfigurationOfPharo itself.
BTW, It's great that we have automated builds.
With the next release of Metacello there will be support for
programmatically updating a config, so if the baseline build runs clean
for pharo dev, the development version could be updated automagically
... folks would always be able to load the dev version and know that at
least the tests ran clean and that you are within a safe distance of the
absolute bleeding edge...
Dale
