Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #96804 > unrolled thread

Re: Automating Sphinx generated documentation

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Automating Sphinx generated documentation Peter Otten <__peter__@web.de> - 2015-09-18 08:56 +0200

#96804 — Re: Automating Sphinx generated documentation

David Aldrich wrote:

> I have setup Sphinx for my Python project. We keep all our code and
> documentation in Subversion. So, following changes to the Python code, I
> need to regenerate and commit the Sphinx generated documentation.
> 
> I just wondered how people manage this.  I'm thinking of using Jenkins (a
> continuous integration tool) to check for changes, regenerate the docs and
> check them in.
> 
> Any suggestions please?

VCS typically have a few hooks to trigger scripts. I found

"Making the Most of Commit Hooks with Subversion"
http://www.linux-mag.com/id/7151/

Maybe you can use one of these to trigger a rebuilt of the  docs.

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web