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

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

    Details

    • Similar Issues:

      Description

      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 Jenkinsfile Part2 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 with warnings ng plugin

       

        Attachments

          Activity

          Hide
          jenkinskin Ankush Pandit added a comment -

          Added jsresult.txt

          Show
          jenkinskin Ankush Pandit added a comment - Added jsresult.txt
          Hide
          drulli Ulli Hafner added a comment -

          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?

          Show
          drulli Ulli Hafner added a comment - 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?
          Hide
          jenkinskin Ankush Pandit added a comment - - edited

          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?

          Show
          jenkinskin Ankush Pandit added a comment - - edited 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?
          Hide
          drulli Ulli Hafner added a comment -

          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.

          Show
          drulli Ulli Hafner added a comment - 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.
          Hide
          jenkinskin Ankush Pandit added a comment -

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

          Show
          jenkinskin Ankush Pandit added a comment - O that make sense. That did fix it. Thanks for your help on this!

            People

            • Assignee:
              drulli Ulli Hafner
              Reporter:
              jenkinskin Ankush Pandit
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: