Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354030 - [releng] Investigate ways to reduce releng disk space usage
Summary: [releng] Investigate ways to reduce releng disk space usage
Status: CLOSED INVALID
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-05 13:39 EDT by Andrew Niefer CLA
Modified: 2019-04-11 02:39 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Niefer CLA 2011-08-05 13:39:51 EDT
We should try and reduce the amount of disk space we use in our releng builds.
Currently we have scripts that clean up old builds and keep only the 3 most recent builds.

Currently:
/shared/eclipse/e4/build/e4/downloads/drops/4.0.0
852M	M20110804-1800    -|
851M	M20110804-0200     |
851M	M20110803-1400     | e4 builds
706M	I20110804-1005     |
697M	I20110729-0200     |
262M	I20110805-1200    -|
141M	scmCache
45G	40builds    <-4.x builds
29G	targets
Comment 1 Andrew Niefer CLA 2011-08-05 13:41:59 EDT
For a given e4 build, the majority of this space is the result of running the tests: 

e4Build@build:/shared/eclipse/e4/build/e4/downloads/drops/4.0.0/I20110729-0200/eclipse-testing> 
201M	eclipse          <- eclipse used to install things into test-eclipse
200M	test-eclipse     <- eclipse instance under test
175M	eclipse-SDK-I20110729-0200-linux-gtk-x86_64.tar.gz

There is no real benefit to keeping these around after the tests are done, individual builds here should clean this up after themselves.

We should keep 
test-eclipse/eclipse/configuration as there may be log files under there.
Comment 2 Andrew Niefer CLA 2011-08-05 13:59:28 EDT
An individual 4.x build is currently around 6G:

/shared/eclipse/e4/build/e4/downloads/drops/4.0.0/40builds/I20110804-1221
2.6 G   I20110804-1221
2.4 G	20110804-1221
1.2 G	eclipse-testing

40builds/I20110804-1221/eclipse-testing is similar to e4 builds in that there are two eclipse installs that can be deleted.  however, there is also a eclipse-testing/I20110804-1221 folder which seems to just be a copy of eclipse-testing (?), doubling everything.

40builds/I20110804-1221/201110804-1221 is all the eclipse installs that were archived to create the build results.  We can probably delete these folders once the individual archives are created.

e4Build@build:/shared/eclipse/e4/build/e4/downloads/drops/4.0.0/40builds/I20110804-1221/20110804-1221/p2temp> 
202672	sdk.install.aix.gtk.ppc64
202568	sdk.install.aix.gtk.ppc
201800	sdk.install.linux.gtk.x86_64
201732	sdk.install.win32.win32.x86
201700	sdk.install.win32.win32.x86_64
201504	sdk.install.linux.gtk.x86
201080	sdk.install.macosx.cocoa.x86
201016	sdk.install.linux.gtk.ppc64
200844	sdk.install.macosx.cocoa.x86_64
200832	sdk.install.hpux.gtk.ia64_32
200796	sdk.install.solaris.gtk.sparc
200720	sdk.install.solaris.gtk.x86

40builds/I20110804-1221/I20110804-1221 are the build results, we should keep everything in here.
Comment 3 Andrew Niefer CLA 2011-08-05 15:50:53 EDT
(In reply to comment #2)
> e4Build@build:/shared/eclipse/e4/build/e4/downloads/drops/4.0.0/40builds/I20110804-1221/20110804-1221/p2temp> 
> 202672    sdk.install.aix.gtk.ppc64
> 202568    sdk.install.aix.gtk.ppc
> 201800    sdk.install.linux.gtk.x86_64
> 201732    sdk.install.win32.win32.x86
> 201700    sdk.install.win32.win32.x86_64
> 201504    sdk.install.linux.gtk.x86
> 201080    sdk.install.macosx.cocoa.x86
> 201016    sdk.install.linux.gtk.ppc64
> 200844    sdk.install.macosx.cocoa.x86_64
> 200832    sdk.install.hpux.gtk.ia64_32
> 200796    sdk.install.solaris.gtk.sparc
> 200720    sdk.install.solaris.gtk.x86

I have made changes to automatically delete these folders after creating the archives.
Comment 4 Eclipse Genie CLA 2019-04-10 19:56:12 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Mickael Istria CLA 2019-04-11 02:39:21 EDT
No more interesting.