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

Details output missing information

    XMLWordPrintable

Details

    Description

      I have your latest jslint plugin and the latest checkstyle plugin running on the latest weekly Jenkins (1.526). Your plugin runs great and I do get the list of errors, but when I click on the details tab on the Checkstyle page, I see:

      foo2.js:69, , Priority: High
      Line too long.

      No description available. Please upgrade to latest checkstyle version.

      foo2.js:101, , Priority: High
      Line too long.

      No description available. Please upgrade to latest checkstyle version.

      Any ideas? I see this for all message types, not just Line too long.

      Attachments

        Activity

          drulli Ulli Hafner added a comment -

          I'm still fixing some other parsers that don't use the columns yet. If you like to test the snapshot version that contains this change: https://buildhive.cloudbees.com/job/jenkinsci/job/warnings-plugin/org.jvnet.hudson.plugins$warnings/

          drulli Ulli Hafner added a comment - I'm still fixing some other parsers that don't use the columns yet. If you like to test the snapshot version that contains this change: https://buildhive.cloudbees.com/job/jenkinsci/job/warnings-plugin/org.jvnet.hudson.plugins$warnings/
          kerrhome Shannon Kerr added a comment -

          That's fine. I checked it out before I uploaded and there is nothing proprietary in it, so we're good. Thanks for letting me know though. Any idea how long until the updated plugin will be available?

          kerrhome Shannon Kerr added a comment - That's fine. I checked it out before I uploaded and there is nothing proprietary in it, so we're good. Thanks for letting me know though. Any idea how long until the updated plugin will be available?
          drulli Ulli Hafner added a comment -

          I hope you don't mind that I used your jslint file for my unit tests.

          drulli Ulli Hafner added a comment - I hope you don't mind that I used your jslint file for my unit tests.

          Code changed in jenkins
          User: Ulli Hafner
          Path:
          pom.xml
          src/main/java/hudson/plugins/warnings/parser/JSLintXMLSaxParser.java
          src/test/java/hudson/plugins/warnings/parser/JSLintParserTest.java
          src/test/java/hudson/plugins/warnings/parser/ParserTester.java
          src/test/resources/hudson/plugins/warnings/parser/jslint/jslint.xml
          http://jenkins-ci.org/commit/warnings-plugin/390dc752c7fffb815e53e305970a4173e055c477
          Log:
          [FIXED JENKINS-19127] Improved JSLint parser to support checkstyle
          format.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/warnings/parser/JSLintXMLSaxParser.java src/test/java/hudson/plugins/warnings/parser/JSLintParserTest.java src/test/java/hudson/plugins/warnings/parser/ParserTester.java src/test/resources/hudson/plugins/warnings/parser/jslint/jslint.xml http://jenkins-ci.org/commit/warnings-plugin/390dc752c7fffb815e53e305970a4173e055c477 Log: [FIXED JENKINS-19127] Improved JSLint parser to support checkstyle format.
          drulli Ulli Hafner added a comment -

          Thanks for attaching. Seems that this JSLint output format is different from the one I'm parsing in the warnings parser. Your format is almost identical to the checkstyle format... Maybe I should include the checkstyle parser in the warnings plug-in, too.

          drulli Ulli Hafner added a comment - Thanks for attaching. Seems that this JSLint output format is different from the one I'm parsing in the warnings parser. Your format is almost identical to the checkstyle format... Maybe I should include the checkstyle parser in the warnings plug-in, too.

          People

            drulli Ulli Hafner
            kerrhome Shannon Kerr
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: