[Pharo-project] [ANN] Hudson build server for Pharo

Stéphane Ducasse stephane.ducasse at inria.fr
Tue Nov 30 10:09:26 CET 2010


> 
> 
> >
> > One question, you have the pharo-project.org domain, why isn't this
> > hudson a subdomain of that domain. Hosted on inria, but accessible by
> > the official project domain?
> >
> One step at a time :-)
> 
> 
> > Anyway, very good news. I suppose that the download page of pharo will
> > point to the latest successful build link of the hudson server very
> > soon.
> 
> 
> Yes... that's the goal. The artefact that people download should be generated completely
> automatically. (This way we can move much faster).
> 
> 
> The Dev images can be automatically generated but shouldn't be consider stable, and should NOT be the dev image that a final user download.
> To build a dev image, you have to options:
> 
> 1) Just load all the latest versions of all external packages with a large gofer script. This way is easiest to just try to build an image and see how it works. But this doesn't scale, this is not reproducible in the future, and what is worst, it can be not stable (not always the latest versions are the required).
> This was the previous way to create a Pharo dev.
> 
> 2) Using Metacello configurations. With this we can make it reproducable and stable. BUUUUT in order to make it stable, we need to define stable metacello versions for all the configuration. And this is not done automatically. 


we should do 1) for now but 2) as soon as we have metacello repositories.
and projects without metacello descriptions will not be published in pharo-dev.

Stef


> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
> 
> 
> 





More information about the Pharo-project mailing list