Like John and other mentors were saying, it's not proper for CI to be a closed/inaccessible environment. Is it running on an Isengard account or in PROD or CORP or just generic EC2? I think that we should remedy this. It's very strange that no committers have access at all. Is there a ticket open to IPSEC?
On Fri, Jan 5, 2018 at 10:17 AM, Marco de Abreu < [email protected]> wrote: > Hello Chris, > > At the moment this is not possible due Amazon AppSec (Application security) > restrictions which does not permit user data and credentials on these > machines. > > I have been thinking about adding single sign on bound to GitHub, but we > would have to check back with AppSec. > > Is the reason for your request still the ability to start and stop running > builds? > > Best regards, > Marco > > Am 05.01.2018 7:11 nachm. schrieb "Chris Olivier" <[email protected]>: > > Marco, > > Are all committers able to get login access to the Jenkins Server? If not, > why? > > -Chris >
