On 13.07.2016 19:11, Jeremy Stanley wrote:
> On 2016-07-13 13:25:44 +0200 (+0200), Markus Zoeller wrote:
>> For some reason the gate docs job didn't find the issue (wrong json
>> format) which got fixed with change [1]. It doesn't even emit a warning.
>> Locally, the execution of "tox -e docs"
On 2016-07-13 13:25:44 +0200 (+0200), Markus Zoeller wrote:
> For some reason the gate docs job didn't find the issue (wrong json
> format) which got fixed with change [1]. It doesn't even emit a warning.
> Locally, the execution of "tox -e docs" does find the issue. Can we make
> the gate docs
On 2016-07-13 13:25, Markus Zoeller wrote:
> For some reason the gate docs job didn't find the issue (wrong json
> format) which got fixed with change [1]. It doesn't even emit a warning.
> Locally, the execution of "tox -e docs" does find the issue. Can we make
> the gate docs job aware of such
On 23.06.2016 12:21, Andreas Jaeger wrote:
> On 06/23/2016 10:43 AM, Markus Zoeller wrote:
>> On 21.06.2016 15:01, Doug Hellmann wrote:
>>> A while back pbr had a feature that let projects pass "warnerror"
>>> through to Sphinx during documentation builds, causing any warnings in
>>> that build to
On 21/06/16 09:01 -0400, Doug Hellmann wrote:
A while back pbr had a feature that let projects pass "warnerror"
through to Sphinx during documentation builds, causing any warnings in
that build to be treated as an error and fail the build. This lets us
avoid things like links to places that
On 2016-06-23 13:44:36 +0200 (+0200), Markus Zoeller wrote:
> Interesting, I didn't know that. It runs without warnings in Nova too,
> so hopefully everything's in a good shape for the pbr release. :)
Note that there has been at least one past proposal[1] to add a
"docs" tox environment as
On 23.06.2016 12:21, Andreas Jaeger wrote:
> On 06/23/2016 10:43 AM, Markus Zoeller wrote:
>> On 21.06.2016 15:01, Doug Hellmann wrote:
>>> A while back pbr had a feature that let projects pass "warnerror"
>>> through to Sphinx during documentation builds, causing any warnings in
>>> that build to
On 06/23/2016 10:43 AM, Markus Zoeller wrote:
On 21.06.2016 15:01, Doug Hellmann wrote:
A while back pbr had a feature that let projects pass "warnerror"
through to Sphinx during documentation builds, causing any warnings in
that build to be treated as an error and fail the build. This lets us
On 21.06.2016 15:01, Doug Hellmann wrote:
> A while back pbr had a feature that let projects pass "warnerror"
> through to Sphinx during documentation builds, causing any warnings in
> that build to be treated as an error and fail the build. This lets us
> avoid things like links to places that
Excerpts from Ihar Hrachyshka's message of 2016-06-21 15:40:45 +0200:
>
> > On 21 Jun 2016, at 15:01, Doug Hellmann wrote:
> >
> > A while back pbr had a feature that let projects pass "warnerror"
> > through to Sphinx during documentation builds, causing any warnings in
> On 21 Jun 2016, at 15:01, Doug Hellmann wrote:
>
> A while back pbr had a feature that let projects pass "warnerror"
> through to Sphinx during documentation builds, causing any warnings in
> that build to be treated as an error and fail the build. This lets us
> avoid
11 matches
Mail list logo