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

JavaDoc console warnings are irgnored

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • warnings-plugin
    • None
    • Debian 3.2.65-1+deb7u2
      Oracle JRE 1.8.0_45-b14
      Jenkins 1.634
      warnings 4.51
      Jenkins gets started by java -jar jenkins.war

    Description

      Although JavaDoc finds errors and these are displayed in the console for that build, the warnings plugin does not show them in its report.

      There are five successful builds in the history before I triggerd the job again. Below i will paste some output from the console:

      [...]
      [javadoc] Generating Javadoc
      [javadoc] Javadoc execution
      [javadoc] Loading source files for package XXX...
      [javadoc] Constructing Javadoc information...
      [javadoc] Standard Doclet version 1.8.0_45
      [javadoc] Building tree for all the packages and classes...
      [javadoc] /home/XXX/.jenkins/jobs/SDK/workspace/Commons/src/de/XXX/XXX/commons/JBossDatasourceController.java:12: error: package org.jboss.as.cli does not exist
      [javadoc] import org.jboss.as.cli.CommandContext;
      [javadoc]                        ^
      [... more Javadoc errors are displayed ...]
      [javadoc] 9 errors
      BUILD SUCCESSFUL
      Total time: 4 seconds
      [... TASKS plugin output ...]
      [WARNINGS] Parsing warnings in console log with parser Java Compiler (javac)
      [WARNINGS] Parsing warnings in console log with parser JavaDoc Tool
      [WARNINGS] Computing warning deltas based on reference build #57
      [WARNINGS] Ignore new warnings since this is the first valid build
      [WARNINGS] Plug-in Resultat: Erfolgreich - Kein Grenzwert wurde ├╝berschritten
      

      As you can see, there are errors but they are either ignored or not found.

      As a side note, many other plugins like TASKS, CHECKSTYLE and FINDBUGS also print "Ignore new warnings since this is the first valid build" during the post build process, so maybe the root of this problem is not the warnings plugin?

      Attachments

        Activity

          bennyprange Benny Prange created issue -
          drulli Ulli Hafner made changes -
          Field Original Value New Value
          Resolution Not A Defect [ 7 ]
          Status Open [ 1 ] Resolved [ 5 ]
          drulli Ulli Hafner made changes -
          Resolution Not A Defect [ 7 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          scm_issue_link SCM/JIRA link daemon made changes -
          Resolution Fixed [ 1 ]
          Status Reopened [ 4 ] Resolved [ 5 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 167898 ] JNJira + In-Review [ 198303 ]

          People

            drulli Ulli Hafner
            bennyprange Benny Prange
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: