Re: [cross-project-issues-dev] The end of an era: shell access.

-issues-dev] The end of an era: shell access. I would like to thank Jonah Graham for helping us to overcome this restriction imposed on us by the Foundation. Thanks Jonah! Greg On Jul 5, 2019, at 9:43 AM, Greg Watson mailto:g.wat...@computer.org>> wrote: I will also add that I’ve had shell

Re: [cross-project-issues-dev] The end of an era: shell access.

I would like to thank Jonah Graham for helping us to overcome this restriction imposed on us by the Foundation. Thanks Jonah! Greg > On Jul 5, 2019, at 9:43 AM, Greg Watson wrote: > > I will also add that I’ve had shell access to build.eclipse.org > for release

Re: [cross-project-issues-dev] The end of an era: shell access.

Thanks Christian! On 12.07.19 15:49, Christian Dietrich wrote: > you can find CBI Jenkinsfiles here: > > https://github.com/eclipse/xtext-lib/blob/master/CBI.Jenkinsfile > https://github.com/eclipse/xtext-core/blob/master/CBI.Jenkinsfile >

Re: [cross-project-issues-dev] The end of an era: shell access.

you can find CBI Jenkinsfiles here: https://github.com/eclipse/xtext-lib/blob/master/CBI.Jenkinsfile https://github.com/eclipse/xtext-core/blob/master/CBI.Jenkinsfile https://github.com/eclipse/xtext-extras/blob/master/CBI.Jenkinsfile

Re: [cross-project-issues-dev] The end of an era: shell access.

Hi Christian, Could you provide a pointer to the scripts, that you have developed? It might help other projects, that are in similar position. Regards, Fred On 05.07.19 11:11, Dietrich, Christian wrote: > From the active committers on Xtext project nobody has shell access > and i can confirm

Re: [cross-project-issues-dev] The end of an era: shell access.

Hi Everyone, First I'd like to apologize for the delay in responding to some of the questions I've seen regarding this change. I chose to notify the community at large because that seemed like the right thing to do. Even though this affects 29 people directly I wanted everyone to be aware

Re: [cross-project-issues-dev] The end of an era: shell access.

Asking again as my question (and its workarounds for the removal of a direct SSH login) appear to have been lost in the haze of panic. :) Will the SFTP access include rsync over SSH, or SSHFS drive mounting? I've dealt with SFTP-only filesystems at Red Hat for years, and it's much less painful

Re: [cross-project-issues-dev] The end of an era: shell access.

I will also add that I’ve had shell access to build.eclipse.org for release engineering for something like 15 years, so this would affect me to the extent that I would be dropping support for the PTP project. If the foundation wants to do this then it should be providing a generic automated

Re: [cross-project-issues-dev] The end of an era: shell access.

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

Re: [cross-project-issues-dev] The end of an era: shell access.

Can you define restricted shell vs shell access? I regularly SSH into build.eclipse.org and losing that access will definitely hurt my capabilities to perform m2e-* maintenance in the short to medium term. On Thu, Jul 4, 2019 at 9:50 PM Eclipse Webmaster < webmas...@eclipse-foundation.org>

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

Re: [cross-project-issues-dev] The end of an era: shell access.

This is _really_ bad news for the Buildship project as well. We have an external CI pipeline set up, which relies on the fact that we have ssh access. Since we use TeamCity, porting everything to Jenkins will be a really big effort. We use the ssh access for two things: uploading jar files and

Re: [cross-project-issues-dev] The end of an era: shell access.

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

Re: [cross-project-issues-dev] The end of an era: shell access.

Mat, Will the SFTP access include rsync over SSH, or SSHFS drive mounting? I've dealt with SFTP-only filesystems at Red Hat for years, and it's much less painful when you can use rsync instead of ftp/scp, or mount an ssh volume to interact more directly with the remote filesystem. (Both are MUCH

Re: [cross-project-issues-dev] The end of an era: shell access.

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:

[cross-project-issues-dev] The end of an era: shell access.

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