• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • p4-plugin
    • None
    • Hudson 1.383
      Perforce plugin 1.1.11
      p4 Rev. P4/LINUX26X86/2009.1/205670 (2009/06/29)

      I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

      The polling log shows:

      Started on Nov 10, 2010 9:29:10 AM
      Looking for changes...
      Using node: builder-ubuntu-jaunty-32-nutmeg
      Using remote perforce client: hudson-unitpp-linux32--497286900
      [unitpp-Linux-32] $ /usr/local/bin/p4 workspace -o hudson-unitpp-linux32--497286900
      Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
      Changing P4 Client View from:

      Changing P4 Client View to:
      //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
      -//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
      -//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
      Done. Took 0.45 sec
      Changes found

          [JENKINS-8064] Perforce plugin incorrectly finds changes

          ickersep created issue -
          ickersep made changes -
          Description Original: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace -o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            -//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            -//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          New: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace -o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            '-//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            '-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          ickersep made changes -
          Description Original: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace -o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            '-//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            '-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          New: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace -o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            -//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            \-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          ickersep made changes -
          Description Original: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace -o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            -//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            \-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          New: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace -o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            \-//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            \-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          ickersep made changes -
          Description Original: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace -o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            \-//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            \-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          New: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace \-o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            \-//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            \-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          ickersep made changes -
          Description Original: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace \-o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            \-//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            \-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          New: I have a project that hasn't changed (no checkins to Perforce), building on a slave (that hasn't changed either). Yet the P4 plugin thinks there are changes and kicks off a build several times a day.

          The polling log shows:

          Started on Nov 10, 2010 9:29:10 AM
          Looking for changes...
          Using node: builder-ubuntu-jaunty-32-nutmeg
          Using remote perforce client: hudson-unitpp-linux32--497286900
          [unitpp-Linux-32] $ /usr/local/bin/p4 workspace \-o hudson-unitpp-linux32--497286900
          Changing P4 Client Root to: /home/boss/hudson/workspace/unitpp-Linux-32
          Changing P4 Client View from:


          Changing P4 Client View to:
            //depot/External/unit++/... //hudson-unitpp-linux32--497286900/...
            \-//depot/External/unit++/Lib/... //hudson-unitpp-linux32--497286900/Lib/...
            \-//depot/External/unit++/Include/... //hudson-unitpp-linux32--497286900/Include/...
          Done. Took 0.45 sec
          Changes found
          Environment New: Hudson 1.383
          Perforce plugin 1.1.11
          p4 Rev. P4/LINUX26X86/2009.1/205670 (2009/06/29)

          Rob Petti added a comment - - edited

          Do changes show up in the changelog of the resulting build?

          Also, does this happen every time the polling runs, or only intermittently? Hudson 1.378 introduced a major master-slave communication issue that is adversely affecting the perforce plugin. It has yet to be fixed, so you will experience problems if you are using the perforce plugin with slaves.

          Rob Petti added a comment - - edited Do changes show up in the changelog of the resulting build? Also, does this happen every time the polling runs, or only intermittently? Hudson 1.378 introduced a major master-slave communication issue that is adversely affecting the perforce plugin. It has yet to be fixed, so you will experience problems if you are using the perforce plugin with slaves.
          Rob Petti made changes -
          Assignee New: Rob Petti [ rpetti ]

          ickersep added a comment -

          No, no changes show up anywhere.

          It happens intermittently. It might very well be that it is related to the master/slave communication issue. I think it started after I upgraded 1.377 to 1.383.

          I downgraded to 1.377 and will see if the problem still happens.

          Do you have a bug number for this master/slave communication bug?

          ickersep added a comment - No, no changes show up anywhere. It happens intermittently. It might very well be that it is related to the master/slave communication issue. I think it started after I upgraded 1.377 to 1.383. I downgraded to 1.377 and will see if the problem still happens. Do you have a bug number for this master/slave communication bug?

          Rob Petti added a comment -

          JENKINS-7809 is the root cause, and JENKINS-7664 is another symptom.

          Rob Petti added a comment - JENKINS-7809 is the root cause, and JENKINS-7664 is another symptom.

            rpetti Rob Petti
            ickersep ickersep
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: