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

Trend graph displayed multiple times

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Not A Defect
    • Component/s: findbugs-plugin
    • Environment:
      Jenkins 2.60 and higher, running on Windows Server 2008 SR3 and on Linux Mint (as a Docker image, based on the official Alpine LTS)
    • Similar Issues:

      Description

      After upgrading a Jenkin test installation (probably from the 2.19 LTS release) i noticed that the FindBugs trend graph showed up twice on a pipeline job that used pipeline script.
       
      To reproduce this problem i cloned a (Maven) test project originally created by Jessie Glick and modified it to run the FindBugs code analysis (https://github.com/selste/simple-maven-project-with-tests, Branch 'findbugs').
       
      When i use declarative pipeline syntax, everything works as expected - and it doesn't matter whether i use the 'Jenkinsfile' or the 'Pipeline script' approach. After at least two successful builds the trend graph is displayed, as shown in the 'declarative.png' screenshot.
      Switching to scripted pipeline syntax leads to a couple of strange effects (see 'scripted.png' screenshot):

      • the trend graph is displayed twice after at least two successful builds
      • the test coverage trend graph is displayed as well even though i did NOT configure this
        The Pipeline definitions - declarative and scripted - are part of the repository.

      I originally posted this as a question on the Jenkins Users group - the thread can be found there: FindBugs Plugin issue with scripted pipeline

      Cheers,

       

      Steffen

        Attachments

          Activity

          Hide
          drulli Ulli Hafner added a comment -

          Please comment your requirements in the corresponding wiki page.

          Show
          drulli Ulli Hafner added a comment - Please comment your requirements in the corresponding wiki page .
          Hide
          selste Steffen Elste added a comment -

          As two coworkers of mine found out after digging around the real culprit is the Pipeline Maven Integration plugin.
          When using the 'withMaven' pipeline step JUnit and FindBugs results will automatically be published, this behaviour can be changed (introduced with 2.3.0) by providing additional parameters.
          This issue can be closed as far as i am concerned.
          Best regards,
           
          Steffen

          Show
          selste Steffen Elste added a comment - As two coworkers of mine found out after digging around the real culprit is the  Pipeline Maven Integration  plugin. When using the 'withMaven' pipeline step JUnit and FindBugs results will automatically be published, this behaviour can be changed (introduced with 2.3.0) by providing additional parameters. This issue can be closed as far as i am concerned. Best regards,   Steffen
          Hide
          drulli Ulli Hafner added a comment -

          Ok, I think with the planned new pipeline features this would have been solved anyway...

          Show
          drulli Ulli Hafner added a comment - Ok, I think with the planned new pipeline features this would have been solved anyway...

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              selste Steffen Elste
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: