Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16883

Doxygen plugin can't find output directory.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not A Defect
    • Major
    • doxygen-plugin
    • None
    • Mac

    Description

      I can't get jenkins to build and publish with the doxygen plugin. I get the error below:

      find . -name *.m -exec grep -i -H XXX '{}' \;
      Archiving artifacts
      Publishing Doxygen HTML results.
      FATAL: error
      hudson.AbortException: The output directory doesn't exist.
      at hudson.plugins.doxygen.DoxygenDirectoryParser.retrieveDoxygenDirectoryFromDoxyfile(DoxygenDirectoryParser.java:354)
      at hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:53)
      at hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:14)
      at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196)
      at hudson.remoting.UserRequest.perform(UserRequest.java:118)
      at hudson.remoting.UserRequest.perform(UserRequest.java:48)
      at hudson.remoting.Request$2.run(Request.java:287)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
      at java.util.concurrent.FutureTask.run(FutureTask.java:138)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      at hudson.remoting.Engine$1$1.run(Engine.java:60)
      at java.lang.Thread.run(Thread.java:680)
      Build step 'Publish Doxygen' changed build result to FAILURE
      An attempt to send an e-mail to empty list of recipients, ignored.
      Finished: FAILURE

      The output directory is the directory where my Doxyfile is.
      I have doxygen installed on my build machine under /usr/local/bin/doxygen.
      My output dir is: OUTPUT_DIRECTORY = myProj/docs/
      My doxyfile is: myProj/docs/Doxyfile

      I've searched and this error seems common, but it looks like it's supposedly fixed in v0.11 which is what I'm running.

      Attachments

        Activity

          People

            gbois Gregory Boissinot
            kemoran Kevin Moran
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: