Opened 16 years ago
Closed 9 years ago
#4740 closed enhancement (fixed)
Accessing the doxygen files in a subversion repository
Reported by: | anonymous | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Component: | DoxygenPlugin |
Severity: | normal | Keywords: | doxygen subversion |
Cc: | Ryan J Ollos | Trac Release: | 0.11 |
Description
As documentation should be part of a project, we commit our doxygen HTML documentation to the subversion repository too. What we do now is to checkout this files on the server in an extra directory to let the doxygen plugin have access to them. The subversion directory could be mounted as WebDAV filesystem, but this means much administration efford too. This means a couple of management and administration, so it would be desirable and highly convenient to access the files directly in the subversion repository. So instead of /var/lib/path/to/doxygen/doc something like svn:trunk/doc/html could then be configured.
Unfortunately I don't know python (I looked at the sources and understood nothing), so I ask you to realize this enhancement.
Thank you in advance!
Attachments (0)
Change History (6)
comment:1 Changed 16 years ago by
Cc: | ryano@… added; anonymous removed |
---|
comment:2 Changed 16 years ago by
Type: | defect → enhancement |
---|
comment:3 Changed 15 years ago by
comment:4 Changed 15 years ago by
Cc: | Ryan J Ollos added; ryano@… removed |
---|
comment:5 Changed 15 years ago by
Instead of a post-commit hook I use Bitten and the following build recipe to generate the latest doxygen documentation and then rsync's them to the SVN host at a location the DoxygenPlugin for Trac is configured to look.
<build xmlns:svn="http://bitten.cmlenz.net/tools/svn" xmlns:sh="http://bitten.cmlenz.net/tools/sh"> <step id="checkout" description="Checkout source from repository"> <svn:checkout url="https://svn/project/" path="${path}" revision="${revision}" /> </step> <step id="build" description="Compile"> <sh:exec executable="doxygen" args=".doxyfile" /> </step> <step id="rsync" description="Update Trac Doxygen"> <sh:exec executable="rsync" args="-rvz --delete /var/local/doxygen/project/ svn@svn:/var/local/doxygen/project" /> </step> </build>
I don't think this is necessary. Manually maintaining the documentation like this is not ideal and takes a lot of time. Try this method instead:
Because the documentation will be generated when the commit is successful, you can be sure that you are always serving the latest/greatest documentation.