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

Allow pipeline configuration to stop trend graphs from rendering

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: warnings-ng-plugin
    • Labels:
      None
    • Environment:
      jenkins 2.71
      latest plugins
    • Similar Issues:
    • Released As:
      6.1.0

      Description

      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:

       

       

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment - - edited

          I.e., you want to disable them by default, and a user can enable them again (as it works in freestyle jobs)?

          Would it be sufficient to make the link to [jenkins]/[job]/tasks/configureDefaults/ somewhere visible?

          Show
          drulli Ulli Hafner added a comment - - edited I.e., you want to disable them by default, and a user can enable them again (as it works in freestyle jobs)? Would it be sufficient to make the link to [jenkins] / [job] /tasks/configureDefaults/ somewhere visible?
          Hide
          drulli Ulli Hafner added a comment -

          Can you please add a comment on the wiki page as well, as I am currently gathering requirements for static analysis in pipelines.

          Show
          drulli Ulli Hafner added a comment - Can you please add a comment on the wiki page as well, as I am currently gathering requirements for static analysis in pipelines .
          Hide
          jredl Jesse Redl added a comment -

          Ulli Hafner yes you have it right. I would love to be able to disable them by default and if a user chose to do so they could enable them again. We have implemented our jenkins pipelines entirely though pipelines as code via the kubernetes-plugin. So, no a link would not be sufficient imo. 

          Show
          jredl Jesse Redl added a comment - Ulli Hafner yes you have it right. I would love to be able to disable them by default and if a user chose to do so they could enable them again. We have implemented our jenkins pipelines entirely though pipelines as code via the kubernetes-plugin. So, no a link would not be sufficient imo. 
          Hide
          drulli Ulli Hafner added a comment -

          I think it makes sense to provide the whole trend graph configuration (UI view currently) as parameters to the new step.

          Show
          drulli Ulli Hafner added a comment - I think it makes sense to provide the whole trend graph configuration (UI view currently) as parameters to the new step.
          Hide
          famod Falko Modler added a comment -

          Any updates on this one?
          We are building a project with > 90 modules incrementally via gitflow-incremental-builder and in that scenario the graphs are more confusing than helpful.

          Show
          famod Falko Modler added a comment - Any updates on this one? We are building a project with > 90 modules incrementally via gitflow-incremental-builder and in that scenario the graphs are more confusing than helpful.

            People

            Assignee:
            drulli Ulli Hafner
            Reporter:
            jredl Jesse Redl
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: