[squeak-dev] Re: Build.squeak.org and squeaksource.com in danger (was Re: [Box-Admins] Disk space usage on box3)

Chris Muller ma.chris.m at gmail.com
Sun Dec 8 20:57:41 UTC 2013


> That's very cool, but it's not the zips we're talking about. We're
> talking about the artifacts produced by Jenkins, which are Squeak
> images. I wrote the release process to produce a series of artifacts
> with different names. Because nothing gets replaced/overwritten, disk
> usage is unbound.

The rate of untamed growth is too fast.

>> The result is that the redundant Magma-backed copy of
>> source.squeak.org consumes less than 1/4th the space of the original
>> File based version.  A Magma-backed copy of squeaksource.com would
>> about 12GB of space.
>>
>> For now, though, Frank has the ability and responsibility to trim up
>> the jenkins stuff.  Thanks Frank.
>
> I nuked the ReleaseSqueakTrunk target directory, freeing up 5.9 GB of
> space. (We should always consider the target/ directory of every job
> as being evanescent. Feel free to nuke these at any time. Every job
> should be written such that it can reconstitute its working
> environment in target/.

Automating something (builds) shouldn't introduce a new manual
process.  There should be something to keep the size reasonable so we
don't have to remember do it manually every month..


More information about the Squeak-dev mailing list