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

P4-plugin not showing changelog for build when one was triggered by SCM

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • p4-plugin
    • Jenkins 2.332.3, Windows server 2016, tomcat v9, Perforce 2015,1, P4-plugin v1.12.4

    Description

      Builds are being triggered by an SCM change but when you look at the details of the build it will say "No changes from last build". The polling log will show that there is a new changelist. This has worked flawlessly for a long time. I've been keeping up with the Jenkins releases along with the plugin updates. 

      Attachments

        1. image-2022-08-12-17-04-01-105.png
          image-2022-08-12-17-04-01-105.png
          36 kB
        2. Jenkins_P4-plugin_1.JPG
          Jenkins_P4-plugin_1.JPG
          27 kB
        3. Jenkins_P4-plugin_2.JPG
          Jenkins_P4-plugin_2.JPG
          50 kB
        4. Jenkins-P4.zip
          170 kB
        5. p4plugin-build56.zip
          188 kB
        6. SCM-polling.txt
          0.6 kB

        Activity

          p4karl Karl Wirth added a comment -

          Hi jfoege 

          Please get me the full console log and screenshots of your job definition.

          If that contains sensitive information please send them in an email to support@perforce.com for the attention of Karl and reference this bug report.

          Regards,

          Karl

          p4karl Karl Wirth added a comment - Hi jfoege   Please get me the full console log and screenshots of your job definition. If that contains sensitive information please send them in an email to support@perforce.com for the attention of Karl and reference this bug report. Regards, Karl
          jfoege Jeff Foege added a comment -

          Karl,

              I added a zip file that has some screen shots and the beginning part of the console log. I didn't attach the whole console log cause I didn't think it would be relevant but if you do want the whole console log then please let me know. I also attached the scm polling log.

          jfoege Jeff Foege added a comment - Karl,     I added a zip file that has some screen shots and the beginning part of the console log. I didn't attach the whole console log cause I didn't think it would be relevant but if you do want the whole console log then please let me know. I also attached the scm polling log.
          p4karl Karl Wirth added a comment -

          Thanks jfoege 

          I took your data and built a test system but I see the changelists. This suggests that it did produce a build log:

          P4: saving built changes.
          Found last change 197054 on syncID bld2_IPI-Trunk
          ---cut---
          ... p4 changes -l -m1 @197067 +
          ... p4 user -o peter.nguyen4 +
          ... p4 describe -s -m51 197067 +
          ... p4 fixes -c197067 +
          ... p4 changes -l -m1 @197055 +
          ... p4 user -o svc.rms.builds +
          ... p4 describe -s -m51 197055 +
          ... p4 fixes -c197055
          ... done 

          Note that 197055 is from a user that you dont want to trigger builds so that may be impacting this but 197067 should be display.

          Please get me the output from:

          p4 describe -s 197055 
          p4 describe -s 197067

          the full console log and the build.xml log for this job execution (to match the console log) from the Jenkins server.

          Again I'm happy to send an email directly to you if this contains sensitive information.

          Regards,

          Karl

           

          p4karl Karl Wirth added a comment - Thanks jfoege   I took your data and built a test system but I see the changelists. This suggests that it did produce a build log: P4: saving built changes. Found last change 197054 on syncID bld2_IPI-Trunk ---cut--- ... p4 changes -l -m1 @197067 + ... p4 user -o peter.nguyen4 + ... p4 describe -s -m51 197067 + ... p4 fixes -c197067 + ... p4 changes -l -m1 @197055 + ... p4 user -o svc.rms.builds + ... p4 describe -s -m51 197055 + ... p4 fixes -c197055 ... done Note that 197055 is from a user that you dont want to trigger builds so that may be impacting this but 197067 should be display. Please get me the output from: p4 describe -s 197055 p4 describe -s 197067 the full console log and the build.xml log for this job execution (to match the console log) from the Jenkins server. Again I'm happy to send an email directly to you if this contains sensitive information. Regards, Karl  
          jfoege Jeff Foege added a comment -

          Karl, I understand its finding new changes submitted. Take a look at one of the images I uploaded "Jenkins_p4plugin_1.jpg" On the main page of the build number it states "No changes from last build" which is incorrect especially if its triggered by a SCM change. It used to list each of the changelists that went into that build. This is very useful if you have to debug something about a current build. 

          jfoege Jeff Foege added a comment - Karl, I understand its finding new changes submitted. Take a look at one of the images I uploaded "Jenkins_p4plugin_1.jpg" On the main page of the build number it states "No changes from last build" which is incorrect especially if its triggered by a SCM change. It used to list each of the changelists that went into that build. This is very useful if you have to debug something about a current build. 
          p4karl Karl Wirth added a comment -

          Hi Jeff,

          Sorry I should have been clearer. What I meant was P4Jenkins is producing the result for Jenkins to display but it's not appearing. Usually this kind of problem is in the 'saving built changes' section. In this case something else has gone wrong, possibly at the Jenkins level. Therefore if you can get me the extra data I might be able to see whats happening:

          Please get me the output from:

          p4 describe -s 197055 
          p4 describe -s 197067

          the full console log and the build.xml log for this job execution (to match the console log) from the Jenkins server.

          Thanks in advance,

          Karl

          p4karl Karl Wirth added a comment - Hi Jeff, Sorry I should have been clearer. What I meant was P4Jenkins is producing the result for Jenkins to display but it's not appearing. Usually this kind of problem is in the 'saving built changes' section. In this case something else has gone wrong, possibly at the Jenkins level. Therefore if you can get me the extra data I might be able to see whats happening: Please get me the output from: p4 describe -s 197055 p4 describe -s 197067 the full console log and the build.xml log for this job execution (to match the console log) from the Jenkins server. Thanks in advance, Karl
          jfoege Jeff Foege added a comment -

          Karl,

             Sorry for the delay. I've been busy trying to get a product tool validation done and then went on a week vacation. Unfortunately the build (#15) we were working with has been removed. I've recently updated Jenkins, Java and the P4 plugin on the build server. A recent build #56 was triggered by an SCM change but still on the build page it lists no changes in build. I've included the full console log, a screen shot of #56, changelog.xml, polling log, p4 describe of the change and the build.xml in the newly uploaded zip file (p4plugin-build56.zip).  I marked for #56 to be kept forever so it doesn't get cycled away. Please let me know if you need more information.

           

          Thx!

          jfoege Jeff Foege added a comment - Karl,    Sorry for the delay. I've been busy trying to get a product tool validation done and then went on a week vacation. Unfortunately the build (#15) we were working with has been removed. I've recently updated Jenkins, Java and the P4 plugin on the build server. A recent build #56 was triggered by an SCM change but still on the build page it lists no changes in build. I've included the full console log, a screen shot of #56, changelog.xml, polling log, p4 describe of the change and the build.xml in the newly uploaded zip file (p4plugin-build56.zip).  I marked for #56 to be kept forever so it doesn't get cycled away. Please let me know if you need more information.   Thx!
          jferrara_viasat Josh Ferrara added a comment -

          jfoege - I stumbled upon this ticket while trying to resolve the same issue: SCM was triggering a build, but all my changelog.xml files were empty and the UI wasn't showing changes. For me, somehow the "Perforce: Query limits" section had the first two options set to 0. After bumping these to a non-zero value, change lists started working again. There was an update to 1.13 of the P4 plugin that seemed to cause this behavior; I see you're running 1.12.4 though so this may not be what's causing your pains.

          jferrara_viasat Josh Ferrara added a comment - jfoege - I stumbled upon this ticket while trying to resolve the same issue: SCM was triggering a build, but all my changelog.xml files were empty and the UI wasn't showing changes. For me, somehow the "Perforce: Query limits" section had the first two options set to 0. After bumping these to a non-zero value, change lists started working again. There was an update to 1.13 of the P4 plugin that seemed to cause this behavior; I see you're running 1.12.4 though so this may not be what's causing your pains.
          jfoege Jeff Foege added a comment -

          jferrara_viasat Thanks for that info! This is what I get for trying to stay current on both Jenkins and the plugins. I'm currently running 1.13 of the plugin and located those settings in "Manage Jenkins > Configure System" and unfortunately I have values in those fields. My changelog.xml has the current changes in it but from the Jenkins UI, if I go to the </> Changes it won't report anything for the build.

          Max number of files in changelist = 50

          Max number changes shown in build = 20

          Head change query limit = 1000.

           

          I wonder if there is some settings somewhere that isn't configured or not configured correctly now. 

          jfoege Jeff Foege added a comment - jferrara_viasat Thanks for that info! This is what I get for trying to stay current on both Jenkins and the plugins. I'm currently running 1.13 of the plugin and located those settings in "Manage Jenkins > Configure System" and unfortunately I have values in those fields. My changelog.xml has the current changes in it but from the Jenkins UI, if I go to the </> Changes it won't report anything for the build. Max number of files in changelist = 50 Max number changes shown in build = 20 Head change query limit = 1000.   I wonder if there is some settings somewhere that isn't configured or not configured correctly now. 

          People

            Unassigned Unassigned
            jfoege Jeff Foege
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: