Re: [openstack-dev] [all] Removal of in progress console log access

On 04/19/2016 12:05 PM, James E. Blair wrote: > Sean Dague writes: > >> Yes, that would let you see the results of an individual experimental >> run that is complete before they all return and post to the change. Once >> they are all done, they are listed on the change, so that's

Re: [openstack-dev] [all] Removal of in progress console log access

Sean Dague writes: > Yes, that would let you see the results of an individual experimental > run that is complete before they all return and post to the change. Once > they are all done, they are listed on the change, so that's good enough. We'll need a Zuul restart for this, so

Re: [openstack-dev] [all] Removal of in progress console log access

On 04/18/2016 12:18 PM, James E. Blair wrote: > Sean Dague writes: > >> On 04/18/2016 11:22 AM, James E. Blair wrote: >>> Sean Dague writes: >>> Bummer. This gets used a to figure out the state of things given that zuul links to the console even after

Re: [openstack-dev] [all] Removal of in progress console log access

Sean Dague writes: > On 04/18/2016 11:22 AM, James E. Blair wrote: >> Sean Dague writes: >> >>> Bummer. This gets used a to figure out the state of things given that >>> zuul links to the console even after the job is complete. Changing that >>> to the log

Re: [openstack-dev] [all] Removal of in progress console log access

On 04/18/2016 11:22 AM, James E. Blair wrote: > Sean Dague writes: > >> Bummer. This gets used a to figure out the state of things given that >> zuul links to the console even after the job is complete. Changing that >> to the log server link would mitigate the blind spot. > >

Re: [openstack-dev] [all] Removal of in progress console log access

Sean Dague writes: > Bummer. This gets used a to figure out the state of things given that > zuul links to the console even after the job is complete. Changing that > to the log server link would mitigate the blind spot. Yeah, we know it's important, which is why we're working

Re: [openstack-dev] [all] Removal of in progress console log access

On 04/15/2016 07:23 PM, Monty Taylor wrote: > tl;dr Effective immediately we've put firewalls in front of the Jenkins > servers removing in-progress console log streaming access > > Longer version > > > Recently some potential security issues have come to our attention with > Jenkins [1] and

[openstack-dev] [all] Removal of in progress console log access

tl;dr Effective immediately we've put firewalls in front of the Jenkins servers removing in-progress console log streaming access Longer version Recently some potential security issues have come to our attention with Jenkins [1] and the way we run it that are non-trivial to fix. As a