|
Jonah,
Yes, the scripts now runs as a Jenkins job once per day:
https://ci.eclipse.org/oomph/job/mirror-index/
So everyone has up-to-date information about how much mirror
space their project is using and can easily identify what they
should consider cleaning up. This usage has gone up 100MB in the
last month. Denis will be very happy if you all go and clean up
your old stuff!
In any case, as others have mentioned, it's not so much an issue
of wanting (or needing) to do things manually but rather the need
(strong desire) for an interactive shell while developing new
functionality.
Regards,
Ed
On 04.07.2019 23:47, Jonah Graham
wrote:
Cool webpage Ed. Thanks for sharing that.
I assume that was generated by some script you
wrote? If so, is there anything that prevents you from
running it via a Jenkins job?
When I first took over releng for CDT it was
at first a little bit of a pain not doing it with shell
access, but instead over time we have moved from manually
running commands on the server to having reproducible
scripts stored in git and run as CI jobs.
My understanding is you will still be able to
run such command/scripts, but only via the CI account. I
trust someone will enlighten me if I am wrong.
Thanks,
Jonah
Mat,
Count me as someone who will be VERY, VERY, VERY
UNHAPPY ABOUT RESTRICTIONS!
Sorry for shouting, but it's hard for me to imagine
how I can maintain the services that I provide without
the access I currently have. Just as an example, I
could not have developed this without such access:
https://download.eclipse.org/oomph/archive/eclipse/index.html
I assume there must be extremely good reasons for
this change of policy, no doubt related to
ultra-secure security. I'm sure those reasons must be
excellent and that you, or someone, will be able to
articulate them. Please do so for the benefit of the
community at large, given that you feel the need to
announce this to the community at large, rather than
to the "limited set of committers".
Perhaps a Bugzilla for such a discussion thread would
be appropriate to reduce noise levels on the mailing
list.
Regards,
Ed
On
04.07.2019 21:49, Eclipse Webmaster wrote:
Hi Everyone,
As some of you may know we have traditionally
provided a limited set of committers with shell
access to build.eclipse.org, and
all other committers having restricted shells.
For the last couple of years[1][2] we've been
working to reduce that number as far as possible,
and the time has come to finish the process.
Effective August 28th 2019 we will be transitioning
all committers that still have a regular shell to
our restricted shell. You will still be able to use
SFTP and SCP to interact with the downloads and
archive areas(but we suggest a job on your Eclipse
CI instance!)
If you have any questions or concerns please feel
free to contact Webmaster.
-Matt.
[1] https://www.eclipse.org/lists/cross-project-issues-dev/msg06625.html
[2] https://www.eclipse.org/lists/eclipse.org-committers/msg01075.html
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
