This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      We are using the warnings plugin in our pipeline as per the following snippet:Ā 

      #!groovy
      
      def call() {
          junit allowEmptyResults: true, testResults: '**/artifacts/results.xml, **/artifacts/jasmine-results.xml'
          step([
              $class: 'WarningsPublisher',
              parserConfigurations: [[
                  parserName: 'PyLint',
                  pattern: '**/artifacts/pylint.out, **/artifacts/pylint_test.out'
              ], [
                  parserName: 'JSLint',
                  pattern: '**/artifacts/jslint.xml'
              ]
          ]])
      }

      It would be greatĀ if we could configure the trend graphs to not display for the pylint and jslint parsers. Maybe something like:

      #!groovy
      
      def call() {
          junit allowEmptyResults: true, testResults: '**/artifacts/results.xml, **/artifacts/jasmine-results.xml'
          step([
              $class: 'WarningsPublisher',
              parserConfigurations: [[
                  parserName: 'PyLint',
                  pattern: '**/artifacts/pylint.out, **/artifacts/pylint_test.out',
                  trendGraph: 'none'
              ], [
                  parserName: 'JSLint',
                  pattern: '**/artifacts/jslint.xml',
                  trendGraph: 'none'
              ]
          ]])
      }

      Ā 

      We care about the warnings themselves and not the trend for these two the graphs add unnecessary clutter to the job statusĀ pages:

      Ā 

      Ā 

            Assignee:
            Ulli Hafner
            Reporter:
            Jesse Redl
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: