Status: Resolved (View Workflow)
Resolution: Not A Defect
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)
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
|Field||Original Value||New Value|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Resolution||Not A Defect [ 7 ]|