[ci server][3.0] #cleanUpForRelease done on server again
Hi, The job https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-1-Tracker/ now does a #cleanUpForRelease using ImageCleaner. This used to be done on update, but that is not good as when people load updates they do not want the side effects of a release clean (mostly, deleting all change set information). So I added command line support for ImageCleaner last week and now that it is in the image, I added this line to the build script: ./pharo Pharo.image clean ârelease This will be used with the next update (#724) The command might be interesting for others, here is the description from the class comment: Usage: clean [ --release ] --release do #cleanUpForRelease --production do #cleanUpForProduction Documentation: This allows to run the ImageCleaner from the commandLine. With no special option it runs Smalltalk cleanUp: true. Usage: pharo Pharo.image clean pharo Pharo.image clean --release
Very cool, it would be very good if the ImageCleaner would enable me to manage what needs to be cleaned. At the moment it is all or nothing. My use case is that I like SUnit to stay in the image. Iâm not only writing module tests while developing but also runtime test cases that monitor the health of the image. It would be wonderful having an easy way to take control of that process. Just an idea for those who have a enough time and no current project to deal with :) Norbert Am 27.01.2014 um 13:28 schrieb Marcus Denker <marcus.denker@inria.fr>:
Hi,
The job
https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-1-Tracker/
now does a #cleanUpForRelease using ImageCleaner. This used to be done on update, but that is not good as when people load updates they do not want the side effects of a release clean (mostly, deleting all change set information).
So I added command line support for ImageCleaner last week and now that it is in the image, I added this line to the build script:
./pharo Pharo.image clean ârelease
This will be used with the next update (#724)
The command might be interesting for others, here is the description from the class comment:
Usage: clean [ --release ] --release do #cleanUpForRelease --production do #cleanUpForProduction
Documentation: This allows to run the ImageCleaner from the commandLine. With no special option it runs Smalltalk cleanUp: true.
Usage: pharo Pharo.image clean pharo Pharo.image clean --release
On 27 Jan 2014, at 14:49, Norbert Hartl <norbert@hartl.name> wrote:
Very cool,
it would be very good if the ImageCleaner would enable me to manage what needs to be cleaned. At the moment it is all or nothing. My use case is that I like SUnit to stay in the image. Iâm not only writing module tests while developing but also runtime test cases that monitor the health of the image. It would be wonderful having an easy way to take control of that process. Just an idea for those who have a enough time and no current project to deal with :)
yes⦠itâs a very ad hoc thing. #cleanUpForProduction needs more work anyway, as lots of packages are dirty after. One of the things that should be changed is to *not* unload SUnit. The time when that was useful is over⦠people like to run tests in deployment more than conserve memory. But in general, this is all very very hackish anyway and what we need it a Pharo that is bootstrapped from a description⦠Marcus
participants (2)
-
Marcus Denker -
Norbert Hartl