I forgot to say the job it triggered by gerrit for every pull request. Sent from my HTC
----- Reply message ----- From: "Andrey Danin" <[email protected]> To: "Ivan Kolodyazhny" <[email protected]>, "fuel-dev" <[email protected]> Subject: Re: [Fuel-dev] Coding guidelines and OpenStack Infra Date: Thu, Dec 12, 2013 09:31 We have a job on fuel-jenkins.mirantis.com which runs flake8 and jslint tests and all results are accessible via Internet. Is it not enough? Sent from my HTC----- Reply message ----- From: "Ivan Kolodyazhny" <[email protected]> To: "fuel-dev" <[email protected]> Subject: [Fuel-dev] Coding guidelines and OpenStack Infra Date: Wed, Dec 11, 2013 13:59 Hi Fuel developers! As you know, OpenStack has own coding guidelines http://docs.openstack.org/developer/hacking/ and our projects are following them. But we have no good enough pep8 and pylint checks for every review request. I propose use OpenStack Jenkins to run pep8 and pylint checks using OpenStack scripts and settings for them like it works for nova ( https://jenkins.openstack.org/view/All/job/gate-nova-pep8/, https://jenkins.openstack.org/view/All/job/gate-nova-pylint/) and other projects. -- Regards, Ivan "e0ne" Kolodyazhny, Software Engineer, Mirantis, Inc.
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
