[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit created an issue

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-07-11 18:42 Priority: Minor Reporter: Ankush Pandit See details here https://superuser.com/questions/1458345/history-only-seems-to-be-pointing-to-the-current-build-when-using-warnings-ng-je Add Comment

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

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner closed an issue as Incomplete

Please add an issue description that actually shows a problem in the plugin.

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ulli Hafner Status: Open Closed Resolution: Incomplete

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Did you click on the provided link? It has screen shots of code and the issue..

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448

History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit See details here [https://superuser.com/questions/1458345/history-only-seems-to-be-pointing-to-the-current-build-when-using-warnings-ng-je]     History only seems to be pointing to the current build when using Warnings NG jenkin plugin and JenkinsFile pipeline. Here is some sudo code from our JenkinsFile [Jenkinsfile Part1|https://i.stack.imgur.com/jrw0N.png] [Jenkinsfile Part2|https://i.stack.imgur.com/nIi8P.png] What we are seeing is that our history graph only seems to be depicting what was caught on the current build and is missing the info from previous builds. Does anyone has any idea on why this is.. [What we are seeing|https://i.stack.imgur.com/pheVR.png] [Even when we have multiple builds that were run before we introduced warnings ng plugin|https://i.stack.imgur.com/JjKyX.png]

Add Comment

[ankush.pandit@cerner.com (JIRA)]

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit reopened an issue

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit Resolution: Incomplete Status: Closed Reopened

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit Attachment: image-2019-07-11-14-03-35-746.png

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Change By: Ankush Pandit

See details here [https://superuser.com/questions/1458345/history-only-seems-to-be-pointing-to-the-current-build-when-using-warnings-ng-je]     History only seems to be pointing to the current build when using Warnings NG jenkin plugin and JenkinsFile pipeline. Here is some sudo code from our JenkinsFile [Jenkinsfile Part1|https://i.stack.imgur.com/jrw0N.png] [Jenkinsfile Part2|https://i.stack.imgur.com/nIi8P.png] What we are seeing is that our history graph only seems to be depicting what was caught on the current build and is missing the info from previous builds. Does anyone has any idea on why this is..

[Even when we have multiple builds that were run before we introduced warnings ng plugin|https://i.stack.imgur.com/JjKyX.png] !image-2019-07-11-14-03-35-746.png!

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated an issue

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ulli Hafner

See details here [https://superuser.com/questions/1458345/history-only-seems-to-be-pointing-to-the-current-build-when-using-warnings-ng-je]     History only seems to be pointing to the current build when using Warnings NG jenkin plugin and JenkinsFile pipeline. Here is some sudo code from our JenkinsFile [Jenkinsfile Part1|https://i.stack.imgur.com/jrw0N.png] [Jenkinsfile Part2|https://i.stack.imgur.com/nIi8P.png] What we are seeing is that our history graph only seems to be depicting what was caught on the current build and is missing the info from previous builds. Does anyone has any idea on why this is.. [Even when we have multiple builds that were run before we introduced warnings ng plugin|https://i.stack.imgur.com/JjKyX.png] !image-2019-07-11-14-03-35-746.png!   Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Are the builds < #161 still available? Did you enable the reports for some builds < #161?

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448

History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit

History only seems to be pointing to the current build when using Warnings NG jenkin plugin and JenkinsFile pipeline. Here is some sudo code from our JenkinsFile [Jenkinsfile Part1|https://i.stack.imgur.com/jrw0N.png] [Jenkinsfile Part2|https://i.stack.imgur.com/nIi8P.png] What we are seeing is that our history graph only seems to be depicting what was caught on the current build and is missing the info from previous builds. Does anyone has any idea on why this is..

[Even when we have multiple builds that were run before we introduced with warnings ng plugin|https://i.stack.imgur.com/JjKyX.png] !image-2019-07-11-14-03-35-746.png!

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit Attachment: image-2019-07-12-08-55-51-376.png

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit Attachment: image-2019-07-12-08-58-15-290.png

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit Attachment: image-2019-07-12-08-59-14-528.png

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Looks like these are available. Can you please explain what you mean by available? We do clean up our workspaces each time after the build using the following code.   cleanWs() dir("${env.WORKSPACE}@tmp") {| |deleteDir()| |}| |dir("${env.WORKSPACE}@script")| |{| |deleteDir()| |} dir("${env.WORKSPACE}@script@tmp") {| |deleteDir()| }   Also you can see that warnings ng config change was introduced in build 159. Also here are the snapshots from build 160 And 159

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Question, where is the data for these graphs being pulled off?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

The data is derived from the Jenkins objects. So if you have an analysis action for #159 and #160, then they should appear in the chart as well.

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Follow up questions. So these Jenkins objects, do they get deleted if we delete the workspace? Where are they stored? If there were any errors while deriving them, where would we see them? How else can I help in figuring out this issue?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

No, they should not. They are stored in the build folder on the Jenkins master. You can call JSON.stringify(echarts.getInstanceByDom(document.getElementById("tools-trend-chart")).getOption()) in the JS console of your browser to see the data of the chart. Paste the JSON here to see what is going on.

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner updated JENKINS-58448

Jenkins / JENKINS-58448

History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ulli Hafner Status: Reopened Open

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Added jsresult.txt

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448

History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit Attachment: jsresult.txt

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Hmm, the x-axis contains the label "07-11", can you please add a file with build numbers as label? Select the button #. Are there any exceptions in Jenkins log?

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit updated an issue

Jenkins / JENKINS-58448

History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ankush Pandit Attachment: buildtxt.txt

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Added the result when displaying the build number on the graph. FYI, This problem occurs with build dates as well. I do not know how to check the jenkins logs, can you please provide instructions?

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit edited a comment on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Added the result when displaying the build number on the graph. FYI, This problem occurs with build dates as well. I do not know how to check the jenkins logs, can you please provide instructions on how to tail them ?

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner resolved as Not A Defect

Jenkins / JENKINS-58448

History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect

Add Comment

[ullrich.hafner@gmail.com (JIRA)]

Ulli Hafner commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline I think I found the problem. In your pipeline you use a variable ID (using the system time). This is wrong you need to use the same ID for all builds, then the results will be correctly mapped. It is clear, if you change the ID in every build then you will never found a sequence of matching builds.

Add Comment

[ankush.pandit@cerner.com (JIRA)]

Ankush Pandit commented on JENKINS-58448

Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline

O that make sense. That did fix it. Thanks for your help on this!

Add Comment