Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 410271

Summary:	"No space left on device"
Product:	Community	Reporter:	Mickael Istria <mistria>
Component:	Hudson sandbox	Assignee:	CI Admin Inbox <ci.admin-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	blocker
Priority:	P3	CC:	marcel.bruch, webmaster
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=410608
Whiteboard:
Bug Depends on:	403843
Bug Blocks:	410154

Description Mickael Istria

2013-06-08 16:03:56 EDT

Since this recent failure on platform-sonar job: https://hudson.eclipse.org/sandbox/job/platform-sonar/6/console , most operations -builds, configs...- on hudson sandbox fail with a no space left on device.

Platform builds seems to require about 25 GB: http://wiki.eclipse.org/Platform-releng/Platform_Build#Free_HDD_space
Some old builds from other jobs could be removed to save some space, but anyway, this hudson sandbox machine seems to need to scale up in term of HDD.

Comment 1 Marcel Bruch

2013-06-10 03:37:27 EDT

Recommenders.gerrit++ also fails:

https://hudson.eclipse.org/sandbox/job/recommenders.gerrit/397/console

Comment 2 Mickael Istria

2013-06-12 09:39:07 EDT

@Webmaster: this is temporarily fixed by disabling the platform-sonar job and removing its workspace. However, enabling this job may produce high-value indicators on platform code and might be a way to think about serious improvement. So I'd really like to be able to run it one day.
Do you have plans to give more disk space for Hudson Sandbox? Any roadmap?

Comment 3 Denis Roy

2013-06-12 10:22:54 EDT

The intention of the sandbox was to casually stage Hudson upgrades and plugins without affecting anyone's work.  However, some projects have taken it as a home to run their production builds.

In the end, HIPP (bug 403843) will render the sandbox mostly obsolete.

Comment 4 Mickael Istria

2013-06-12 10:28:17 EDT

Ok, so the only alternative I see for the moment is to install the Sonar and Gerrit Hudson plugins in Hudson (not sandbox) and migrate all those production jobs on Hudson Sandbox to Hudson. Is this do-able?

Comment 5 Denis Roy

2013-06-12 10:31:27 EDT

We won't run the Gerrit plugin on our production Hudson since we're not yet sure of what the security implications are.  Running the sonar plugin on the production Hudson is a possibility, but won't happen until Kepler has shipped.  In the end, I would have hoped that we could integrate Sonar into the real Platform job, rather than duplicating the job and wasting disk space.

Comment 6 Mickael Istria

2013-06-12 10:38:22 EDT

(In reply to comment #5)
> We won't run the Gerrit plugin on our production Hudson since we're not yet
> sure of what the security implications are.

OK

> Running the sonar plugin on the production Hudson is a possibility, but won't happen until Kepler has shipped.

Ok, it makes sense to avoid risks now.


> In the end, I would have hoped that we could integrate Sonar into the real Platform job, rather than duplicating the job and wasting disk space.

Actually, there's currently no job that builds platform on Hudson: http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg21346.html . So we could create a single platform job that would perform platform build + Sonar analysis. However, it wouldn't be the official build in a first time as it wouldn't publish the output p2 repositories.

Comment 7 Mickael Istria

2013-07-11 03:59:34 EDT

Hudson sandbox is not meant to host production builds, but tests for hudson itself. This report is then a WONTFIX as it is out of the scope of hudson sandbox.