Hi,
I do share Ed and Markus’ opinion. There are many tasks I do with shell access. Restricting will cause losing flexibility to do these jobs. I will have to do these in circuitous(very inefficient) way. I would be very unhappy with these restrictions. Thanks Sravan From: Markus Knauer <mkna...@eclipsesource.com> Sent: Friday, July 05, 2019 2:39 PM To: Cross project issues <cross-project-issues-dev@eclipse.org> Subject: [EXTERNAL] Re: [cross-project-issues-dev] The end of an era: shell access. Hi Matt, I share Ed's opinion: Many of my tasks that are currently easy to accomplish with the flexibility of a shell will become nearly impossible without, and because these tasks require some flexibility I cannot simply replace them with jobs running on a CI instance. And e.g. there's really no benefit of running a rsync in a Jenkins job (with a lot of try and error involved) compared to do the same work in an efficient manner from the shell. Thanks, Markus On Thu, 4 Jul 2019 at 22:54, Ed Merks <ed.me...@gmail.com <mailto:ed.me...@gmail.com> > wrote: 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 <http://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@eclipse.org <mailto:cross-project-issues-dev@eclipse.org> 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@eclipse.org <mailto:cross-project-issues-dev@eclipse.org> 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@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
