Sven Van Caekenberghe-2 wrote
The test.image contains all your project specific code, and loading the config just checks all dependencies and only loads what has changed, incrementally. It only takes some 10s of seconds.
It never occurred to me that this was the way to go, but the config handler does it by default. Maybe it is just me, but I had the impression that everybody (including CIs) always built from scratch (more or less, there were staged systems), while it is actually quite practical to keep on updating the same image for a much faster turn around.
Ah, I see. The speed is very nice, but what about e.g. class-side initialization? i.e. if a class>>initialize has changed, the update will not be run, no. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Stroke-of-genius-tp4681471p4681578.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.