Lukas, This is interesting. Is there any way to find the script that was run to build a particular image? What separates the successful and stable builds from the unstable ones? What (how bad) is a fail build?
You load Shout (which is a must<g>). Otherwise, how similar is the image to Pharo-dev + Seaside? Is there a way to get the bleeding edge of Pharo and a stable version of Seaside? Is the reported "last duration" (41 min) the time it took to create the image? Bill ________________________________________ From: [email protected] [[email protected]] On Behalf Of Lukas Renggli [[email protected]] Sent: Saturday, June 12, 2010 11:18 AM To: [email protected] Subject: Re: [Pharo-project] FW: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta > You are already producing 1.2. The core is at 1.1 RC - that's great! But > here in the trenches, there is nothing approximating a dev image beta, and I > can't figure out how to build it. Then I need a Seaside-enabled image on top > of that. There is very little of value I can do with a release until Seaside > is present. The daily Seaside builds are based on PharoCore1.1rc1. http://hudson.lukas-renggli.ch/job/Seaside%203.0/lastSuccessfulBuild/artifact/seaside3/*zip*/seaside3.zip Lukas -- Lukas Renggli www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
