Re: [openstack-dev] [infra][keystone][kolla][bandit] linters jobs

2016-02-11 Thread Steven Dake (stdake)
Andreas, Totally understand the overload problem with no short-term workarounds. I think all engineering in OpenStack is over capacity a bit and folks are really burning the midnight oil to make sure Mitaka is the best release of OpenStack yet! Please feel free to drop by #kolla and ping the cor

Re: [openstack-dev] [infra][keystone][kolla][bandit] linters jobs

2016-02-11 Thread Andreas Jaeger
On 2016-02-11 02:50, Joshua Hesketh wrote: > Hey Andreas, > > Why not keep pep8 as an alias for the new linters target? Would this > allow for a transition path while work on updating the PTI is done? pep8 and linters do different work in infra, and infra calls pep8. A project can have both... I

Re: [openstack-dev] [infra][keystone][kolla][bandit] linters jobs

2016-02-10 Thread Joshua Hesketh
Hey Andreas, Why not keep pep8 as an alias for the new linters target? Would this allow for a transition path while work on updating the PTI is done? Cheers, Josh On Thu, Feb 11, 2016 at 6:55 AM, Andreas Jaeger wrote: > Hi, > > the pep8 target is our usual target to include style and lint chec

[openstack-dev] [infra][keystone][kolla][bandit] linters jobs

2016-02-10 Thread Andreas Jaeger
Hi, the pep8 target is our usual target to include style and lint checks and thus is used besides pep8 also for doc8, bashate, bandit, etc as documented in the PTI (=Python Test Interface, http://governance.openstack.org/reference/cti/python_cti.html). We've had some discussions to introduce a ne