This is interesting. Â Is there any way to find the script that was run to build a particular image?
The scripts are here: http://github.com/renggli/builder/tree/master/scripts
What separates the successful and stable builds from the unstable ones?
Unstable builds are builds that have failing tests (or too many code critics errors).
What (how bad) is a fail build?
Filing builds are builds that could not be completed (missing package, compile error, ...).
You load Shout (which is a must<g>). Â Otherwise, how similar is the image to Pharo-dev + Seaside?
Probably quite different. I load packages and set settings according to my preference.
Is there a way to get the bleeding edge of Pharo and a stable version of Seaside?
Not from my server, but you could setup one that builds whatever you need. For me, I use ... - ... the latest release candidate or stable release of Pharo only. - ... the latest package versions for code I am working on (RB, OB, Seaside, Magritte, Pier, ...)
Is the reported "last duration" (41 min) the time it took to create the image?
Yes, this includes the time to run the tests (and code critics). Lukas -- Lukas Renggli www.lukas-renggli.ch