Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #96804
| From | Peter Otten <__peter__@web.de> |
|---|---|
| Subject | Re: Automating Sphinx generated documentation |
| Date | 2015-09-18 08:56 +0200 |
| Organization | None |
| References | <41302A7145AC054FA7A96CFD03835A0A0B9D749B@EX10MBX02.EU.NEC.COM> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.23.1442559418.16376.python-list@python.org> (permalink) |
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.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Automating Sphinx generated documentation Peter Otten <__peter__@web.de> - 2015-09-18 08:56 +0200
csiph-web