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

Changes are missing in every job after update to 2.426.3

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • None

      I upgraded Jenkins to 2.426.3.

      After upgrade, there is "No changes from last build." message printed in changes tab of Jenkins job.

      Even though Polling job is polled by scm change, I can not see changes in both status and changes tab. 

      In api/xml page, there is 
      <changeSet _class="org.jenkinsci.plugins.p4.changes.P4ChangeSet"/>
      but I can not see <item _class="org.jenkinsci.plugins.p4.changes.P4ChangeEntry">
      I tried with P4 plugin on both 1.13.3 version and 1.15.1 version.

          [JENKINS-72842] Changes are missing in every job after update to 2.426.3

          Andy H added a comment - - edited

          Collating the required data.

          patdhaval30 p4karl Ticket ref: 01289245 

          Andy H added a comment - - edited Collating the required data. patdhaval30 p4karl Ticket ref: 01289245 

          Eric Boehm added a comment -

          FWIW, in our case, we eventually traced this to a bad perforce credential in the Source Management section of the job configuration.

          Changes were populated once we fixed the credentials

          You might want to verify/test your credential through the credential interface, if you haven't done so already.

          Eric Boehm added a comment - FWIW, in our case, we eventually traced this to a bad perforce credential in the Source Management section of the job configuration. Changes were populated once we fixed the credentials You might want to verify/test your credential through the credential interface, if you haven't done so already.

          Andy H added a comment - - edited

          em_boehm This kind of makes sense, but if the credential was wrong would we not expect the build to fail as it would be unable to retrieve files from P4.

           

          Andy H added a comment - - edited em_boehm This kind of makes sense, but if the credential was wrong would we not expect the build to fail as it would be unable to retrieve files from P4.  

          Eric Boehm added a comment -

          We were able to checkout files but for some reason the credential stored in the job prevented the changes from being updated. Possibly because we have 

          P4PORT

          P4TICKETs

          P4TRUST 

          defined globally in Jenkins (/configure as envrionment variables)

          If you go to 

          Manage Jenkins > Credentials > System > Global credentials (unrestricted)

          and click on your perforce credential and then Update, you will see a 'Test Connection' button at the bottom, right hand side.

          You can use this button to verify that you configured the credential correctly.

           

          Eric Boehm added a comment - We were able to checkout files but for some reason the credential stored in the job prevented the changes from being updated. Possibly because we have  P4PORT P4TICKETs P4TRUST  defined globally in Jenkins (/configure as envrionment variables) If you go to  Manage Jenkins > Credentials > System > Global credentials (unrestricted) and click on your perforce credential and then Update, you will see a 'Test Connection' button at the bottom, right hand side. You can use this button to verify that you configured the credential correctly.  

          Andy H added a comment -

          em_boehm Thanks for the assistance

          Test credential is successful, I'll look for anything errant with regards P4PORT 

          Andy H added a comment - em_boehm Thanks for the assistance Test credential is successful, I'll look for anything errant with regards P4PORT 

          Dhaval added a comment -

          andyh200  Is it working after em_boehm suggestions?

          Dhaval added a comment - andyh200   Is it working after em_boehm suggestions?

          Andy H added a comment -

          Sadly not, experiencing the same results.

          Testing the credentials shows as successful, yet still see no changes.

          Andy H added a comment - Sadly not, experiencing the same results. Testing the credentials shows as successful, yet still see no changes.

          Andy H added a comment -

          Came up with a couple of theories earlier, unsure how to prove them though

          The plugin no longer receives the change list details when requested.
          The plugin doesn’t interact correctly with the Jenkins API to update the latest changes.

          Andy H added a comment - Came up with a couple of theories earlier, unsure how to prove them though The plugin no longer receives the change list details when requested. The plugin doesn’t interact correctly with the Jenkins API to update the latest changes.

          Dhaval added a comment -

          andyh200 We have planned to analyze your logs. Thanks for sending them. Will get back to you in coming weeks.

          Dhaval added a comment - andyh200 We have planned to analyze your logs. Thanks for sending them. Will get back to you in coming weeks.

          Dhaval added a comment - - edited

          andyh200 We checked the log, changes are visible in logs, not sure why its not visible in UI. We are checking this.
          Changes are being taken, it is not visible in UI.

          Dhaval added a comment - - edited andyh200 We checked the log, changes are visible in logs, not sure why its not visible in UI. We are checking this. Changes are being taken, it is not visible in UI.

            Unassigned Unassigned
            zpdleotl Kihoon
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: