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

Last Build is ignored when specifying "Pin build at Perforce Label"

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • p4-plugin
    • None
    • Jenkins 1.641

      When specifying "Pin build at Perforce Label" in order to get the changes up to specific revision, the "summary of changes" includes way more checking than it should be from last build.

          [JENKINS-40747] Last Build is ignored when specifying "Pin build at Perforce Label"

          Paul Allen added a comment -

          Please can you confirm the P4 plugin version, there have been a few recent fixes for calculating last built change. If you recently upgraded you may need to run a Build Now to help update Jenkins records for the last build.

          When using the "Pin build..." option if the Jenkins Job had not been executed for a while then the next build will include all changes from the last build. The last build data is stored in the build.xml file.

          Paul Allen added a comment - Please can you confirm the P4 plugin version, there have been a few recent fixes for calculating last built change. If you recently upgraded you may need to run a Build Now to help update Jenkins records for the last build. When using the "Pin build..." option if the Jenkins Job had not been executed for a while then the next build will include all changes from the last build. The last build data is stored in the build.xml file.

          boris avney added a comment - - edited

          I think we've figured out the issue, it looks like our miss. P4 displays all checkins since last successful build. Meaning the user will see this and previous failed build commits.

          p4paul - Thanks for that quick reply anyway

          boris avney added a comment - - edited I think we've figured out the issue, it looks like our miss. P4 displays all checkins since last successful build. Meaning the user will see this and previous failed build commits. p4paul - Thanks for that quick reply anyway

          Paul Allen added a comment -

          Hi Boris,

          You are not the only one to notice this; perhaps I should change the behaviour.  I am reopening the issues to see what others think.  I'm open to suggestions...

          Kind regards,

          Paul

          Paul Allen added a comment - Hi Boris, You are not the only one to notice this; perhaps I should change the behaviour.  I am reopening the issues to see what others think.  I'm open to suggestions... Kind regards, Paul

          Code changed in jenkins
          User: Paul Allen
          Path:
          src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java
          http://jenkins-ci.org/commit/p4-plugin/1074b987b92faa5dfb5412cc7e034cfad7b177b6
          Log:
          Only reports changes since the last build.

          Previously the build summary reported all changes since the last
          successful build.

          JENKINS-40747

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java http://jenkins-ci.org/commit/p4-plugin/1074b987b92faa5dfb5412cc7e034cfad7b177b6 Log: Only reports changes since the last build. Previously the build summary reported all changes since the last successful build. JENKINS-40747

          Paul Allen added a comment -

          Released 1.6.1

          Paul Allen added a comment - Released 1.6.1

            p4paul Paul Allen
            borisa boris avney
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: