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

Bug 359759

Summary:	Builds should be published using a cron job
Product:	z_Archived	Reporter:	Matt Heitz <mheitz>
Component:	EDT	Assignee:	Project Inbox <edt.builds-inbox>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	jspadea, svihovec
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Matt Heitz

2011-10-03 15:38:38 EDT

Our builds are copied to the downloads directory by Hudson during the "publish" step of the build.  See org.eclipse.edt.releng\promote-N.properties.  It copies the files directly to the build machine, thanks to an ACL on the downloads filesystem.  This is a bad idea, see http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg06491.html

We should remove the ACL, publish to a directory on the build machine, and set up a cron job to copy from the build machine to the downloads area.

We should also have the cron job clean up old builds.  Files from the nightly builds pile up in a few locations on build.eclipse.org.  They need to be removed periodically so we don't waste too much space.  At the moment, builds are placed in ~/downloads/edt/downloads/drops/nightly/0.7.0/N_ThisBuild/ and also the features and plugins directories under ~/downloads/edt/updates/nightly/.

There are also some old builds in ~/downloads/edt/downloads/drops/nightly/0.7.0 which I don't have permission to delete.  Need an admin to do it for me.

Comment 1 Matt Heitz

2011-10-05 09:20:53 EDT

Builds should publish to a directory under /shared, where there's lots of disk space.  Then the cron job can move the files to /downloads.

Comment 2 Matt Heitz

2011-11-28 11:08:00 EST

The old nightly builds have been deleted.

Comment 3 Matt Heitz

2012-02-24 10:30:33 EST

Update http://wiki.eclipse.org/EDT:Release_Engineering when this is done.