Hi Travis,

>1. For performance reasons it'd be nice to reduce duplication across all of 
>these builds, but it doesn't look like Sphinx supports multiple builders in a 
>single run.

What did you mean "duplication"?
Surely Sphinx does not support to invoke multiple builders in a single
run. But Sphinx supports incremental build. So second or later builds
reuse the result of first build.
So you can save a time on multiple builds.

> 2. The more important issue is how to accumulate issues across multiple runs 
> (ignoring duplicates from files that always get re-parsed). My guess is that 
> the way to accomplish will be squelching output from all but the last run, 
> pickling or otherwise writing to disc all of the accumulated errors across 
> each run, and then supplying a config variable with the final run to output 
> the summary of these issues.

There are no way to do that. Please save the output of each execution
of sphinx-build.

Thanks,
Takeshi KOMIYA

2017-02-23 0:28 GMT+09:00 Travis Everett <[email protected]>:
> Hi all,
>
> I'm working on a conversion project with support for blocking a CI build on
> certain doc infractions and printing out tables summarizing the lint
> codes/severity/locations. We'll already be building 3 output formats and I'd
> also like to have the option to tack on something like the linkcheck
> builder. I'm curious if/how others have approached these kinds of
> duplication, and whether you've run into any gotchas:
>
> 1. For performance reasons it'd be nice to reduce duplication across all of
> these builds, but it doesn't look like Sphinx supports multiple builders in
> a single run.
>
> 2. The more important issue is how to accumulate issues across multiple runs
> (ignoring duplicates from files that always get re-parsed). My guess is that
> the way to accomplish will be squelching output from all but the last run,
> pickling or otherwise writing to disc all of the accumulated errors across
> each run, and then supplying a config variable with the final run to output
> the summary of these issues.
>
> Thanks for any advice,
> Travis
>
> --
> You received this message because you are subscribed to the Google Groups
> "sphinx-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/sphinx-users.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"sphinx-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sphinx-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to