Sam,
Adding the cbi-dev mailing list, as your question is a good one.
On 2019-04-15 6:13 p.m., Sam Davis
wrote:
Given that there is no longer shell access to build.eclipse.org,
what is the recommended way to do this cleanup? Create Jenkins
build jobs that list directory contents in the console, decide
what can be deleted, and then create another job to do the
deletion?
We really need a file browsing mechanism, but in the meanwhile,
your suggestion of using Jenkins jobs is how I recommend you do
it. It's clunky, but it's all we have right now.
Denis
Sam
--
Sam Davis
Senior Software Engineer, Tasktop
Committer, Eclipse Mylyn
http://tasktop.com
Folks,
The disk footprint of mirrored
content on download.eclipse.org
is up to 1.4TB. We need to do a better job (much better)
of keeping it small. I've filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=546434
to track this.
-------- Forwarded Message --------
Hi
Eclipse Mirror team,
Currently
eclipse mirror is ~1.4 TB, surpassing both debian
and ubuntu in size.
Is
it possible to create a more compact rsync module
containing most requested files?
For
example OpenSuse has "hotstuff" modules for mirrors
who want to provide value while conserving space and
downstream sync bandwidth. (i.e. I don't like to
download 375 versions of a file -over the life time
of the mirror- for that single person over there
using that project, they can go to the main mirror
for that file)
--
Gokdeniz
Karadag
_______________________________________________
eclipse.org-committers mailing list
eclipse.org-committers@xxxxxxxxxxx
https://www.eclipse.org/mailman/listinfo/eclipse.org-committers
IMPORTANT: Membership in this list is generated by processes
internal to the Eclipse Foundation. To be permanently removed
from this list, you must contact emo@xxxxxxxxxxx to request
removal.
|