cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <da...@gnsa.us>
Subject [JENKINS] Thoughts on purging some binaries and some jobs
Date Thu, 16 Aug 2012 20:01:43 GMT
Hi folks,

Jenkins has begun complaining about available disk space, so I figured
I'd start looking.

See below how the various jobs are consuming space.
Some of these jobs are keeping as many as 20 copies of built binaries,
and many of these jobs are a bit outdated (the 2.2.x and 2.2.y builds
must be building against the old github repo)

I am proposing that we delete any 2.2 or 3.0 jobs and make the the
standard that we'll only keep around the 3 most recent builds.

Thoughts, comments, flames?

--David


467M    ./build-api-docs-2.2.x
652M    ./build-marvin
644M    ./build-cloudstack-4.0
756M    ./test-junit-4.0
1.7G    ./build-api-docs-2.2.y
794M    ./build-docs-master
660M    ./build-api-docs-4.0
787M    ./junit-test
1.1G    ./build-api-docs-3.0.x
484M    ./test-smoke-4.0
1.9G    ./build-api-docs-master
764M    ./test-junit
615M    ./checkstyle
491M    ./build-docs-devguide-master
488M    ./CloudStack
1.2G    ./Simple_build
1.3G    ./jobs
16K     ./lost+found
1.2G    ./Automated Test Runs
424M    ./marvin-test

Mime
View raw message