Hi,
based on this thread I've came into the situation to be blocked by a
filled up Windows Server
(https://builds.apache.org/computer/windows-2012-1/) which is filled up
again..
So I have taken the liberty to wipe out the workspaces of the following
projects:
flex-flexunit (maven)
flex-flexunit (maven)
flex-sdk-converter (maven)
flex-tool-api (maven)
Mesos-Reviewbot-Windows(No workspace there)
Mesos-Windows
Royale-asjs
Royale-compiler
Royale-typedefs
Kind regards
Karl Heinz Marbaise
Apache Maven PMC
On 14/07/18 12:00, Karl Heinz Marbaise wrote:
Hi Joan,
thanks for starting such thread...
I've seen also many issues about that...and the Maven Team is been
affected by them...
and I have started to change our global Jenkins lib to handle that...
cause I think we have many build so in the end we will consume a lot of
disk space.
Based on the issues I have done some calculations for our Maven builds..
We have 96 Components/Plugins etc. which means first 96 Jobs (multi
branch pipelines)..
At least a master for each of those above things which means lowest
number of builds is 96 (lets say for the sake of convenience 100) ...but
for each of them we are building
with JDK 7, JDK 8, JDK 9 and JDK 10 (see [2]) which results at minimum
into:
4 * 100 Builds (workspaces)...and that's not all...
So I think it would be great to have such list of disk space usage on
the nodes related to the projects/jobs ...
@INFRA
Is there a way I could get this information on my own (without bothering
INFRA team) to see if my changes are helping ?
Kind regards
Karl Heinz Marbaise
Apache Maven PMC
[1]: https://builds.apache.org/view/M-R/view/Maven/job/maven-box/
[2]:
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-acr-plugin/job/master/workflow-stage/
On 14/07/18 07:29, Joan Touzet wrote:
Hi there,
Chris over in https://issues.apache.org/jira/browse/INFRA-16768
recommended I start a thread.
We've been getting increasing numbers of failures on our builds
due to nodes running out of disk space. In 16768, Chris says:
"We are getting to the point where builds are running machines out of
space faster than we can clear them out. I've cleaned up H24 a bit.
We'll discuss further, but this is going to take some cooperation
amongst all builders to start purging workspaces."
So this is the requested thread. What do we, collectively, as
Jenkins users, need to do to clean out workspaces? I'm
fairly sure that CouchDB workspaces are pretty clean, since we
do the bulk of our builds in /tmp and try our best to clean up
after failed builds. But I am happy to admit I don't know
everything I should or shouldn't be doing.
Chris, would a list of the "top offenders" be useful? I'm not
looking to shame anyone, but shedding a little light on the
approaches that are the biggest problem might help.
-Joan
