Ok, it is broken indeed:
� � � http://jenkins.lukas-renggli.ch/job/Seaside%203.0%20(Metacello)/3/console
At starting point I use a normal Pharo 1.3, but with e tests unloaded.
On Wednesday, 19 October 2011, Dale Henrichs <dhenrich@vmware.com> wrote:
> Great!
>
> Yes...that's the one ...I've subscribe to the rss feed for the Metacello build (Looks like you kicked one off already) so I'll be able to respond to those issues...
>
> Presumably you'll trigger builds not only when the config changes, but when underlying platform changes as well? Or is it better to schedule it to build once a day (or when config changes)?
I can observe a single directory per project. Should I trigger the build with changes to the Metacello repository? My machine cannot handle too many builds. It is old and very slow.
Lukas
>
>
> Dale
> ----- Original Message -----
> | From: "Lukas Renggli" <renggli@gmail.com>
> | To: Pharo-project@lists.gforge.inria.fr
> | Sent: Tuesday, October 18, 2011 2:44:58 PM
> | Subject: Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3
> |
> | > It would be useful if you used the ConfigurationOfSeaside30 and
> | > ConfigurationOfGrease in your continuous integration server for
> | > seaside. There have been a number of issues that would have been
> | > uncovered much earlier if you included the configurations in your
> | > tests ...
> |
> | I can do that. Which one?
> |
> | Gofer new
> | � � squeaksource: 'MetacelloRepository';
> | � � package: 'ConfigurationOfSeaside30';
> | � � load.
> | (Smalltalk at: #ConfigurationOfSeaside30) load.
> |
> | Lukas
> |
> | --
> | Lukas Renggli
> | www.lukas-renggli.ch
> |
> |
>
>
--
Lukas Renggli
www.lukas-renggli.ch