Last modified: 2014-09-03 09:07:52 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T27978, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 25978 - Jenkins: Set up generated php documentation for MediaWiki extensions
Jenkins: Set up generated php documentation for MediaWiki extensions
Status: NEW
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-11-17 17:01 UTC by Sam Reed (reedy)
Modified: 2014-09-03 09:07 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Sam Reed (reedy) 2010-11-17 17:01:49 UTC
It'd be useful to have a doxygen install for extensions.

Or have the current one list extensions too

Is this possible?
Comment 1 Max Semenik 2010-11-17 17:05:13 UTC
I think that extensions should be separate, lots of them aren't well-maitained and would just create needless noise.
Comment 2 Sam Reed (reedy) 2010-11-17 17:06:30 UTC
+shell, cc'ing Ryan (As I imagine he'd be likely the one to sort it)
Comment 3 Chad H. 2010-11-17 17:07:59 UTC
Maybe we could (ab)use @package and @subpackage for grouping them? Shouldn't be
hard to add it to the cron that updates svn.w.o/doc/

Maybe svn.w.o/extension-doc/?
Comment 4 Ryan Lane 2010-11-17 17:09:10 UTC
Well, I'll take care of it, when we decide if we want to do it or not :)
Comment 5 Niklas Laxström 2010-11-17 17:52:56 UTC
Translate extension already has its own documentation located elsewhere with preferred configuration.

It isn't much use to create documentation for extensions which are not documented with documentation in mind. Case-by-case basis seems reasonable though, but how much work is it to maintain it
Comment 6 Sam Reed (reedy) 2010-11-17 17:54:13 UTC
Indeed. I was after it whilst working on CodeReview, would've been good to be able to have documentation open in a different window on a different monitor
Comment 7 Mark A. Hershberger 2011-10-16 17:57:19 UTC
(In reply to comment #4)
> Well, I'll take care of it, when we decide if we want to do it or not :)

After some discussion, we've decided this is something we want, so can you take care of this now?
Comment 8 Ryan Lane 2011-10-16 20:59:54 UTC
Can someone describe what I'm supposed to be doing, and how I'm supposed to do it?
Comment 9 Chad H. 2012-11-08 21:51:47 UTC
Moving to testing infrastructure since we want Jenkins to do this sort of stuff.
Comment 10 Krinkle 2013-06-25 18:59:54 UTC
Right now our gen script has an option to include/exclude locally installed extensions, but not to exclude core itself.

Assuming the generated documentation works standalone (e.g. without including core for cross-reference in the same output) we should be able to do this.

Then we can enable the build step from the postmerge pipeline of an extension that would like this autogenerated and published to doc.wikimedia.org (like we already do for core).
Comment 11 Niklas Laxström 2013-06-26 07:22:40 UTC
For Translate extension [2] we have been using TAGFILES [1] to do cross references.

[1] TAGFILES = /home/betawiki/doxygen-tagfile.xml=http://svn.wikimedia.org/doc 
[2] http://translatewiki.net/docs/Translate/html/ (but apparently the tagfile handling is currently broken)
Comment 12 Antoine "hashar" Musso (WMF) 2013-06-26 16:23:54 UTC
TAGFILES is described in Doxygen documentation 'Linking to external documentation' at http://www.stack.nl/~dimitri/doxygen/manual/external.html
Comment 13 Nemo 2014-09-02 11:46:38 UTC
(In reply to Niklas Laxström from comment #5)
> Translate extension already has its own documentation located elsewhere

But no longer, "Generated on Tue Oct 29 00:00:23 2013" (cf. https://gerrit.wikimedia.org/r/#/c/157791/ ).

Looks trivial to do in Tools as we already have an extensions checkout; will try later.
Comment 14 Nemo 2014-09-03 09:07:52 UTC
(In reply to Nemo from comment #13)
> Looks trivial to do in Tools as we already have an extensions checkout

It is, once you throw enough memory at it. :-)
https://tools.wmflabs.org/mediawiki-mirror/html/dirs.html (I'll set up a daily update)
Configuration adapted from translatewiki.net, with some heavy features removed for faster browsing: https://tools.wmflabs.org/mediawiki-mirror/doxygen.conf
Warnings (https://tools.wmflabs.org/mediawiki-mirror/warn.doxygen.log ):

$ grep -Eo "warning:.+" warn.doxygen.log | sort | uniq -c | sort -nr | head -40
    911 warning: Found unknown command `\group'
    873 warning: Found unknown command `\Elastica'
    743 warning: Found unknown command `\dataProvider'
    574 warning: Found unknown command `\covers'
    349 warning: Found unknown command `\Query'
    323 warning: member with no name found.
    315 warning: Found unknown command `\licence'
    213 warning: Found unknown command `\access'
    198 warning: Found unknown command `\expect'
    174 warning: Found unknown command `\Builder'
    142 warning: Found unknown command `\expectedException'
    131 warning: missing argument after \category.
    126 warning: no uniquely matching class member found for 
    112 warning: Unexpected end of comment while inside link command
     87 warning: no matching class member found for 
     75 warning: Found unknown command `\Filter'
     74 warning: Found unknown command `\Exception'
     70 warning: Found unknown command `\Response'
     64 warning: Found unknown command `\depends'
     48 warning: Found unknown command `\InvalidException'
     47 warning: Found unknown command `\TODO'
     47 warning: Found unknown command `\Document'
     47 warning: Found unknown command `\Bulk'
     44 warning: Found unknown command `\Facet'

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links