[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds

0 views
Skip to first unread message

ravage@bluewin.ch (JIRA)

unread,
Aug 6, 2019, 8:48:02 AM8/6/19
to jenkinsc...@googlegroups.com
Marc Würth created an issue
 
Jenkins / Bug JENKINS-58826
"Aggregated Analysis Results" does not get updated after a few dozen builds
Issue Type: Bug Bug
Assignee: Ulli Hafner
Attachments: grafik.png, grafik2.png
Components: warnings-ng-plugin
Created: 2019-08-06 12:47
Environment: Jenkins ver. 2.187

Ubuntu 16.04 64-bit

os.name Linux
os.version 4.4.0-157-generic

java.vendor Oracle Corporation
java.version 1.8.0_212
java.vm.info mixed mode
java.vm.name OpenJDK 64-Bit Server VM
java.vm.version 25.212-b03

Plugins:
JavaScript GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1
Pipeline (workflow-aggregator): 2.6
Jackson 2 API Plugin (jackson2-api): 2.9.9.1
Git plugin (git): 3.10.1
Maven Integration plugin (maven-plugin): 3.3
Ant Plugin (ant): 1.9
Credentials Plugin (credentials): 2.2.0
JSch dependency plugin (jsch): 0.1.55
JavaScript GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1
Delivery Pipeline Plugin (delivery-pipeline-plugin): 1.4.0
JavaScript GUI Lib: Moment.js bundle plugin (momentjs): 1.1.1
Email Extension Plugin (email-ext): 2.66
Build Keeper Plugin (build-keeper-plugin): 1.3
Lockable Resources plugin (lockable-resources): 2.5
Parameterized Trigger plugin (parameterized-trigger): 2.35.2
DTKit 2 API. (dtkit-api): 2.1.1-1
Token Macro Plugin (token-macro): 2.8
jQuery plugin (jquery): 1.12.4-0
Clover plugin (clover): 4.10.0
Pipeline Graph Analysis Plugin (pipeline-graph-analysis): 1.10
GIT server Plugin (git-server): 1.7
Violations plugin (violations): 0.7.11
OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5
Pipeline: Step API (workflow-step-api): 2.20
Pipeline: Multibranch (workflow-multibranch): 2.21
Folders Plugin (cloudbees-folder): 6.9
Javadoc Plugin (javadoc): 1.5
Job Configuration History Plugin (jobConfigHistory): 2.22
Warnings Next Generation Plugin (warnings-ng): 5.3.0
JDepend Plugin (jdepend): 1.3.0
Clover PHP plugin (cloverphp): 0.5
Crap4J plugin (crap4j): 0.9
SCM API Plugin (scm-api): 2.6.3
Authentication Tokens API Plugin (authentication-tokens): 1.3
Git client plugin (git-client): 2.8.0
Branch API Plugin (branch-api): 2.5.3
JIRA plugin (jira): 3.0.8
Pipeline: Declarative (pipeline-model-definition): 1.3.9
Mailer Plugin (mailer): 1.23
Plain Credentials Plugin (plain-credentials): 1.5
Build Pipeline Plugin (build-pipeline-plugin): 1.5.8
SSH Credentials Plugin (ssh-credentials): 1.17.1
Infrastructure plugin for Publish Over X (publish-over): 0.22
Pipeline: Declarative Extension Points API (pipeline-model-extensions): 1.3.9
External Monitor Job Type Plugin (external-monitor-job): 1.7
Pipeline: Job (workflow-job): 2.33
xUnit plugin (xunit): 2.3.5
Matrix Project Plugin (matrix-project): 1.14
Script Security Plugin (script-security): 1.61
JavaScript GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1
Matrix Authorization Strategy Plugin (matrix-auth): 2.4.2
Display URL API (display-url-api): 2.3.1
Pipeline: Groovy (workflow-cps): 2.72
Trilead API Plugin (trilead-api): 1.0.4
HTML Publisher plugin (htmlpublisher): 1.18
JDK Tool Plugin (jdk-tool): 1.2
Active Directory plugin (active-directory): 2.16
SSH Slaves plugin (ssh-slaves): 1.30.0
Static Analysis Utilities (analysis-core): 1.96
Pipeline: Nodes and Processes (workflow-durable-task-step): 2.32
Pipeline: Input Step (pipeline-input-step): 2.10
Durable Task Plugin (durable-task): 1.30
Rich Text Publisher Plugin (rich-text-publisher-plugin): 1.4
Throttle Concurrent Builds Plug-in (throttle-concurrents): 2.0.1
PAM Authentication plugin (pam-auth): 1.5.1
Pipeline: Build Step (pipeline-build-step): 2.9
Analysis Model API Plug-in (analysis-model-api): 5.2.0
Pipeline: Stage Step (pipeline-stage-step): 2.3
Task Scanner Plug-in (tasks): 4.53
Pipeline: Basic Steps (workflow-basic-steps): 2.18
Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1
Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.14
Command Agent Launcher Plugin (command-launcher): 1.3
Docker Pipeline (docker-workflow): 1.18
Pipeline: SCM Step (workflow-scm-step): 2.9
Shelve Project Plugin (shelve-project-plugin): 2.4
Pipeline: Model API (pipeline-model-api): 1.3.9
Checkstyle Plug-in (checkstyle): 4.0.0
Structs Plugin (structs): 1.19
Subversion Plug-in (subversion): 2.12.2
LDAP Plugin (ldap): 1.20
Publish Over SSH (publish-over-ssh): 1.20.1
Apache HttpComponents Client 4.x API Plugin (apache-httpcomponents-client-4-api): 4.5.5-3.0
Pipeline: Declarative Agent API (pipeline-model-declarative-agent): 1.1.1
Pipeline: REST API Plugin (pipeline-rest-api): 2.11
Docker Commons Plugin (docker-commons): 1.15
Run Condition Plugin (run-condition): 1.2
Plot plugin (plot): 2.1.1
Pipeline: API (workflow-api): 2.35
Icon Shim Plugin (icon-shim): 2.0.3
bouncycastle API Plugin (bouncycastle-api): 2.17
Credentials Binding Plugin (credentials-binding): 1.19
PMD Plug-in (pmd): 4.0.0
MapDB API Plugin (mapdb-api): 1.0.9.0
Pipeline: Stage View Plugin (pipeline-stage-view): 2.11
DRY Plug-in (dry): 3.0.0
Conditional BuildStep (conditional-buildstep): 1.3.6
JUnit Plugin (junit): 1.28
WMI Windows Agents Plugin (windows-slaves): 1.4
Pipeline: Stage Tags Metadata (pipeline-stage-tags-metadata): 1.3.9
Pipeline: Supporting APIs (workflow-support): 3.3
Labels: plugin jenkins warnings graph
Priority: Minor Minor
Reporter: Marc Würth

On one the new pipelines, I just experienced a problem. With each build, the various issues (PMD, Open Tasks, CPD & Styles) get recorded and up until build #79 (currently at #108), it also updated the "Aggregated Analysis Results" graph.
But out ot nowhere it doesn't get updated now.
I didn't change the Jenkinsfile all day, also didn't change any server side configuration. Not even restarted Jenkins or something.

Here, you see the PHPCPD graph going up to #107 but the "Aggregated Analysis Results" only go up to #79.
I checked the logs of build 78 up to 81 but haven't found any clue in there.
I tried to locate the related file(s) for the aggregated graph on disk, but didn't find any.
I just created a new branch and it still works there:

Part of our Jenkinsfile:

[...]
always {
	[...]
	recordIssues([
		healthy: 25,
		unhealthy: 100,
		sourceCodeEncoding: 'UTF-8',
		tools: [
			pmdParser(
				id: 'phpmd',
				name: 'PHPMD',
				pattern: 'build/logs/pmd.xml',
				reportEncoding: 'UTF-8'
			)
		]
	])
	recordIssues([
		healthy: 1,
		unhealthy: 50,
		sourceCodeEncoding: 'UTF-8',
		tools: [
			checkStyle(
				id: 'phpcs',
				name: 'PHPCS',
				pattern: 'build/logs/checkstyle.xml',
				reportEncoding: 'UTF-8'
			)
		]
	])
	recordIssues([
		healthy: 5,
		unhealthy: 250,
		sourceCodeEncoding: 'UTF-8',
		tools: [
			taskScanner(
				normalTags: 'TODO,@todo',
				highTags: 'FIXME,@fixme',
				ignoreCase: true,
				includePattern: 'bin/**/*.php,config/**/*.php,src/**/*.php,src/**/*.ctp,plugins/**/*.php,plugins/**/*.ctp,resources/**/*.php,tests/**/*.php,tests/**/*.ctp'
			)
		]
	])
	recordIssues([
		healthy: 5,
		unhealthy: 100,
		sourceCodeEncoding: 'UTF-8',
		tools: [
			cpd(
				id: 'phpcpd',
				name: 'PHPCPD',
				highThreshold: 100,
				normalThreshold: 50,
				pattern: 'build/logs/pmd-cpd.xml',
				reportEncoding: 'UTF-8'
			)
		]
	])
}
[...]

 

 This was reported first on Gitter.

https://gitter.im/jenkinsci/warnings-plugin?at=5d41f24b4ba6af0b02661dd9

You can write me on Gitter, if you want.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

ullrich.hafner@gmail.com (JIRA)

unread,
Aug 6, 2019, 3:20:02 PM8/6/19
to jenkinsc...@googlegroups.com
Ulli Hafner commented on Bug JENKINS-58826
 
Re: "Aggregated Analysis Results" does not get updated after a few dozen builds

Can you please check if in your build.xml file the following text is present

<io.jenkins.plugins.analysis.core.model.AggregationAction plugin="warnings-ng

You can use grep:

grep io.jenkins.plugins.analysis.core.model build.xml

Then we see the other actions from my plugin as well.

The build.xml file is part of the jobs folder of your Jenkins master.
E.g. on my machine:
{{/Users/hafner/Development/git/warnings-ng-plugin-devenv/docker/volumes/jenkins-home/jobs/pipeline-analysis-model/lastStable
}}

ullrich.hafner@gmail.com (JIRA)

unread,
Aug 6, 2019, 3:21:02 PM8/6/19
to jenkinsc...@googlegroups.com
Ulli Hafner edited a comment on Bug JENKINS-58826
Can you please check if in your build.xml file the following text is present
{noformat}
<io.jenkins.plugins.analysis.core.model.AggregationAction plugin="warnings-ng
{noformat}

You can use grep:
{noformat}
grep io.jenkins.plugins.analysis.core.model build.xml
{noformat}

Then we see the other actions from my plugin as well.

The build.xml file is part of the jobs folder of your Jenkins master.
E.g. on my machine:
{ { noformat}
/Users/hafner/Development/git/warnings-ng-plugin-devenv/docker/volumes/jenkins-home/jobs/pipeline-analysis-model/lastStable
{noformat } }

ullrich.hafner@gmail.com (JIRA)

unread,
Aug 6, 2019, 3:21:03 PM8/6/19
to jenkinsc...@googlegroups.com

ravage@bluewin.ch (JIRA)

unread,
Aug 7, 2019, 6:17:01 AM8/7/19
to jenkinsc...@googlegroups.com

Ulli Hafner

It is a multibranch pipeline project, so I found the file for the last successful here:

/var/lib/jenkins/jobs/PROJECT/branches/trunk/builds/121 (the newest build)

# grep io.jenkins.plugins.analysis.core.model build.xml
    <io.jenkins.plugins.analysis.core.model.ResultAction plugin="warni...@5.3.0">
    </io.jenkins.plugins.analysis.core.model.ResultAction>
    <io.jenkins.plugins.analysis.core.model.ResultAction plugin="warni...@5.3.0">
        <minimumSeverity reference="../../../io.jenkins.plugins.analysis.core.model.ResultAction/healthDescriptor/minimumSeverity"/>
    </io.jenkins.plugins.analysis.core.model.ResultAction>
    <io.jenkins.plugins.analysis.core.model.ResultAction plugin="warni...@5.3.0">
            <edu.hm.hafner.analysis.Severity reference="../../../../../io.jenkins.plugins.analysis.core.model.ResultAction/result/sizePerSeverity/entry/edu.hm.hafner.analysis.Severity"/>
        <minimumSeverity reference="../../../io.jenkins.plugins.analysis.core.model.ResultAction/healthDescriptor/minimumSeverity"/>
    </io.jenkins.plugins.analysis.core.model.ResultAction>
    <io.jenkins.plugins.analysis.core.model.ResultAction plugin="warni...@5.3.0">
            <edu.hm.hafner.analysis.Severity reference="../../../../../io.jenkins.plugins.analysis.core.model.ResultAction/healthDescriptor/minimumSeverity"/>
            <edu.hm.hafner.analysis.Severity reference="../../../../../io.jenkins.plugins.analysis.core.model.ResultAction/result/sizePerSeverity/entry/edu.hm.hafner.analysis.Severity"/>
        <minimumSeverity reference="../../../io.jenkins.plugins.analysis.core.model.ResultAction/healthDescriptor/minimumSeverity"/>
    </io.jenkins.plugins.analysis.core.model.ResultAction>
    <io.jenkins.plugins.analysis.core.model.AggregationAction plugin="warni...@5.3.0"/>

I even compared the file with its siblings from previous builds (before the bug) and other branches (working). I haven't found significant differences, just updated references and such.

 

ullrich.hafner@gmail.com (JIRA)

unread,
Sep 19, 2019, 4:51:32 AM9/19/19
to jenkinsc...@googlegroups.com

Is this still a problem with the 6.x version?

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

ullrich.hafner@gmail.com (JIRA)

unread,
Sep 19, 2019, 4:52:02 AM9/19/19
to jenkinsc...@googlegroups.com

ravage@bluewin.ch (JIRA)

unread,
Sep 25, 2019, 5:52:01 AM9/25/19
to jenkinsc...@googlegroups.com

Yes, it is still a problem.

The  diagram hasn't changed, even though we use 6.0.4 now.

ullrich.hafner@gmail.com (JIRA)

unread,
Oct 1, 2019, 5:49:03 PM10/1/19
to jenkinsc...@googlegroups.com

I think I found the problem: the chart stops exactly after showing the results of 50 builds. This is a fixed size limit for the trend charts. In the aggregation chart somehow the build results are sorted the other way around (and not from the last to the first). This happens for the dashboard portly as well.

ullrich.hafner@gmail.com (JIRA)

unread,
Oct 1, 2019, 5:50:02 PM10/1/19
to jenkinsc...@googlegroups.com
Ulli Hafner edited a comment on Bug JENKINS-58826
I think I found the problem: the chart stops exactly after showing the results of 50 builds. This is a fixed size limit for the trend charts. In the aggregation chart somehow the build results are sorted the other way around (and not from the last to the first). This happens for the dashboard portly portlet as well.  

ullrich.hafner@gmail.com (JIRA)

unread,
Oct 1, 2019, 5:50:03 PM10/1/19
to jenkinsc...@googlegroups.com
Ulli Hafner started work on Bug JENKINS-58826
 
Change By: Ulli Hafner
Status: Open In Progress

ullrich.hafner@gmail.com (JIRA)

unread,
Oct 1, 2019, 5:50:04 PM10/1/19
to jenkinsc...@googlegroups.com

ravage@bluewin.ch (JIRA)

unread,
Oct 2, 2019, 7:28:02 AM10/2/19
to jenkinsc...@googlegroups.com
Marc Würth commented on Bug JENKINS-58826
 
Re: "Aggregated Analysis Results" does not get updated after a few dozen builds

Ulli Hafnernot sure if your hypothesis is true. The screenshot disagrees with you. It shows more than 50 builds. But may be I did not understand correctly. You probably know better.

ullrich.hafner@gmail.com (JIRA)

unread,
Oct 2, 2019, 7:35:09 AM10/2/19
to jenkinsc...@googlegroups.com

Well I did not count every dot in the chart, I just thought it is almost 50. The counter is only effective for not deleted builds with a result.

ullrich.hafner@gmail.com (JIRA)

unread,
Oct 2, 2019, 11:32:11 AM10/2/19
to jenkinsc...@googlegroups.com

ullrich.hafner@gmail.com (JIRA)

unread,
Oct 7, 2019, 9:12:03 AM10/7/19
to jenkinsc...@googlegroups.com
Ulli Hafner resolved as Fixed
Change By: Ulli Hafner
Status: In Progress Resolved
Resolution: Fixed
Released As: 6.1.1

ravage@bluewin.ch (JIRA)

unread,
Oct 7, 2019, 9:31:02 AM10/7/19
to jenkinsc...@googlegroups.com
Marc Würth updated an issue
Change By: Marc Würth
Attachment: image-2019-10-07-15-30-25-143.png

ravage@bluewin.ch (JIRA)

unread,
Oct 7, 2019, 9:32:02 AM10/7/19
to jenkinsc...@googlegroups.com
Marc Würth commented on Bug JENKINS-58826
 
Re: "Aggregated Analysis Results" does not get updated after a few dozen builds

Ulli Hafnerthe problem seems to be fixed. The aggregated graph got updated.

Thank you very much and greetings from Basel, Switzerland.

Reply all
Reply to author
Forward
0 new messages