On Mon, Jul 13, 2020 at 8:49 AM Daniel Shahaf <[email protected]>
wrote:
>...
> Also, why seven? I'd rather keep as many builds as needed to go back
>
I just threw out a number, to start the conversation.
> to before the branching point of the latest stable release. It's not
> going to be that much disk space, is it? Assuming we discard .bz2 files
> to save some disk space ("Let them use gzip!"):
>
> 20MB/nightly * 1 nightly/month * 24 months[minor line release period] =
> 0.5GB
>
As I said: the space is likely not going to be an issue. The primary
question is "what do we want to retain?"
> (Don't know where your 50MB figure is from; on dist/ it's 25MB/release.)
>
$ ls -laF r1784492/
total 51276
drwxr-xr-x 2 buildmaster buildmaster 4096 Feb 27 2017 ./
drwxr-xr-x 293 buildmaster buildmaster 12288 Feb 27 2017 ../
-rwxr-xr-x 1 buildmaster buildmaster 15559956 Feb 27 2017
subversion-nightly.tar.bz2*
-rwxr-xr-x 1 buildmaster buildmaster 40 Feb 27 2017
subversion-nightly.tar.bz2.sha1*
-rwxr-xr-x 1 buildmaster buildmaster 18534901 Feb 27 2017
subversion-nightly.tar.gz*
-rwxr-xr-x 1 buildmaster buildmaster 40 Feb 27 2017
subversion-nightly.tar.gz.sha1*
-rwxr-xr-x 1 buildmaster buildmaster 18360378 Feb 27 2017
subversion-nightly.zip*
-rwxr-xr-x 1 buildmaster buildmaster 40 Feb 27 2017
subversion-nightly.zip.sha1*
-rwxr-xr-x 1 buildmaster buildmaster 13087 Feb 27 2017
svn_version.h.dist-nightly*
Mark notes else-thread that this hasn't worked in a long while. So maybe we
simply disable it, until there is a call for nightly builds?
Note: distinct from build/test and report build success/failure. ... this
is about storing builds for people to access/test.
Cheers,
-g
