Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] Action required: mirror size

Hi Denis


Moving P2 repos to archive is unhelpful for a user who attempts a Maven build from the archive repo.

The first Bug above is a Tycho fix for the original OCL Bug report. Alternatively the EF could ignore a non-archive p2.mirrorsURL so that the archived repo behaves just as if the archiving had stripped the p2.mirrorsURL.


Ed Willink

On 13/04/2020 14:51, Denis Roy wrote:


As is mirrored worldwide, is it important to keep your download footprint to a minimum. Most of our mirror sites are also host to a number of OSS projects, and enterprise disk space is not cheap. Some strategies to note:

- Nightly, weekly, milestone and RC builds should be deleted

- Older releases must be moved to If moved into the same directory structure, links typically do not need to be updated, as our 404 Not Found handlers will look for the file in the archives before throwing the error.

- Please use this compiled Archive index (courtesy of the Oomph team) to find your project's mirror footprint:

The risk of not cleaning up is significant. Mirrors, looking to liberate disk space, will simply purge the worst offenders, and with fewer mirror sites offering Eclipse bits, our servers must handle more downloads, which means unnecessary expense for the Eclipse Foundation.

Many thanks for your cooperation.



Denis Roy

Director, IT Services | Eclipse Foundation, Inc.

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Twitter: @droy_eclipse

_______________________________________________ mailing list
To unsubscribe from this list, visit


Back to the top