Re: [openstack-dev] [docs] rethinking docs jobs in the gate

2015-02-16 Thread Sean Dague
On 02/16/2015 10:38 AM, Christian Berendt wrote: On 02/16/2015 04:29 PM, Andreas Jaeger wrote: For documentation projects we should discuss this separately as well, Is it possible to keep all environments like they are and to add a meta environment (called docs) calling the existing

Re: [openstack-dev] [docs] rethinking docs jobs in the gate

2015-02-16 Thread Andreas Jaeger
On 02/16/2015 04:36 PM, Doug Hellmann wrote: When we talked about this in the review of the governance change to set tox -e docs as part of the testing interface for a project, jeblair (and maybe others) pointed out that we didn't want projects running extra steps when their docs were built.

[openstack-dev] [docs] rethinking docs jobs in the gate

2015-02-16 Thread Sean Dague
I've noticed a proliferation of docs jobs on projects in the gate now - https://review.openstack.org/#/c/154737/ gate-trove-tox-checknicenessSUCCESS in 2m 34s gate-trove-tox-checksyntax SUCCESS in 2m 51s gate-trove-tox-checkdeletions SUCCESS in 2m 11s

Re: [openstack-dev] [docs] rethinking docs jobs in the gate

2015-02-16 Thread Doug Hellmann
On Mon, Feb 16, 2015, at 10:05 AM, Sean Dague wrote: I've noticed a proliferation of docs jobs on projects in the gate now - https://review.openstack.org/#/c/154737/ gate-trove-tox-checknicenessSUCCESS in 2m 34s gate-trove-tox-checksyntax SUCCESS in 2m 51s

Re: [openstack-dev] [docs] rethinking docs jobs in the gate

2015-02-16 Thread Christian Berendt
On 02/16/2015 04:29 PM, Andreas Jaeger wrote: For documentation projects we should discuss this separately as well, Is it possible to keep all environments like they are and to add a meta environment (called docs) calling the existing environments? This way we can reduce the number of jobs on