Last modified: 2013-04-09 02:14:17 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 T35524, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33524 - Jenkins: Publish error output of Doxyxgen
Jenkins: Publish error output of Doxyxgen
Product: Wikimedia
Classification: Unclassified
Continuous integration (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Krinkle
Depends on:
Blocks: documentation
  Show dependency treegraph
Reported: 2012-01-04 21:02 UTC by Tim Landscheidt
Modified: 2013-04-09 02:14 UTC (History)
2 users (show)

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


Description Tim Landscheidt 2012-01-04 21:02:01 UTC
When run on MediaWiki's codebase, doxygen outputs copious warnings about functions/classes/etc. missing documentation altogether, wrong doxygen syntax, and function arguments defined, but undocumented or documented, but not defined.

  It would be nice if these could be included in Jenkins a) to guide some developers' love to this and b) to see its development over time.

  There is a "Doxygen Plugin" but it just seems to provide some links to the documentation instead of parsing the doxygen log.  The "Warnings Plugin" on the other hand claims to support doxygen.  I think it would be useful if the output looked similar to the PMD warnings (or were integrated there).
Comment 1 Sam Reed (reedy) 2012-01-04 21:25:57 UTC
Having it somewhere centralised, like Jenkins seems to make sense

Obviously, we have our doxygen install, but we don't display those errors anywhere publically (AFAIK)

I know some developers (including myself) have numerous ways of looking for bad documentation, ranging from running doxygen locally, to IDEs
Comment 2 Krinkle 2013-04-09 02:14:17 UTC
A few weeks back I moved out legacy doxygen install on to It now runs from a postmerge setup from Zuul/Jenkins (instead of a cronjob).

The error output is available in two places:

1) The console output in the build history:

2) Sterr and stdout are written to files as build artificats,
   published on

  for the most recent gathering of Doxygen warnings.

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