If
there are resources available to work on this, it would be
much better if download.eclipse.org served as central
gateway to both the primary download server and the archive.
Then one can implement all sort of archiving policies
without involving projects or affecting end users
referencing these URLs… You can auto-archive based on age,
you can auto-archive based on demand, heck you can even pick
a goal for how much to mirror and have a heuristic that
shuffles between primary and archive to meet that goal.
-
Konstantin
Does it make sense to consider moving files
that are old--say three or more years old--to the archive
server automatically?
Wayne
On 06/19/2012 10:33 AM, Denis Roy wrote:
To help you
clean up older builds and files from the Eclipse download
server, I've compiled a list of files that are actually
sync'ed to our mirrors.
http://download.eclipse.org/technology/phoenix/download.eclipse.org-filelist.txt.gz
I each project to look at the file list, and either remove
files that are no longer needed, or move older releases[1] to
the archives.
Thanks,
Denis
[1] http://wiki.eclipse.org/IT_Infrastructure_Doc#Downloads