Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: p4-plugin
    • Environment:
      Docker Jenkins as master, Windows Server 2016 + Java 1.8.0 144 b0 and Gentoo as slaves
    • Similar Issues:

      Description

      Client is created and sync of client appears in log but the files are not there. I need to log into node and issue p4 sync manually.

        Attachments

          Activity

          Hide
          matthew_dews Matthew Dews added a comment -

          Also ran into this issue recently. William's workaround works for us at the moment. According to our admin the Perforce server has parallel sync on unless a client requests otherwise.

          Windows 10 x86 (virtualized)
          Jenkins Service runs as a local user
          Job that that had failing p4 sync was run locally
          1 macOS slave which we have observed no sync issues on
          P4 Plugin 1.9.3
          Jenkins 2.138.2
          java.runtime.version 1.8.0_144-b01

          Show
          matthew_dews Matthew Dews added a comment - Also ran into this issue recently. William's workaround works for us at the moment. According to our admin the Perforce server has parallel sync on unless a client requests otherwise. Windows 10 x86 (virtualized) Jenkins Service runs as a local user Job that that had failing p4 sync was run locally 1 macOS slave which we have observed no sync issues on P4 Plugin 1.9.3 Jenkins 2.138.2 java.runtime.version 1.8.0_144-b01
          Hide
          newtopian Eric Daigneault added a comment -

          Still an issue, 

          Jenkins 2.176.2

          p4 plugin: 1.10.3

          perforce server: Server version: P4D/LINUX26X86_64/2018.1/1673397 (2018/06/21)

          simply changed the job to put false in the parallel sync and it worked

          Show
          newtopian Eric Daigneault added a comment - Still an issue,  Jenkins 2.176.2 p4 plugin: 1.10.3 perforce server: Server version: P4D/LINUX26X86_64/2018.1/1673397 (2018/06/21) simply changed the job to put false in the parallel sync and it worked
          Hide
          wbrode William Brode added a comment -

          Doug Whitfield or Arkady English - what was the resolution of your issue?  We are seeing similar behavior so it could help us.

          Show
          wbrode William Brode added a comment - Doug Whitfield or Arkady English - what was the resolution of your issue?  We are seeing similar behavior so it could help us.
          Hide
          douglasawh Doug Whitfield added a comment -

          William Brode we did not get the logs in that particular case.

           

          Show
          douglasawh Doug Whitfield added a comment - William Brode we did not get the logs in that particular case.  
          Hide
          kroutley Kurt Routley added a comment -

          One of our teammates is seeing this again, although their automation stack is on an older version of the p4 plugin and p4d, but based on the p4java release notes it should have sufficient parallel sync support. They hit the issue where sync would run and report success in automation, however the files were not actually sync'd, and it wasn't resolved until they explicitly set the sync configuration to have parallel sync enabled, but with threads, minimum files, and minimum bytes all set to 0.

          Environment information:

          Running Jenkins 2.164.2 with P4 Plugin 1.7.4 (uses p4java 2017.2.1535715) and SCM API Plugin 2.6.3.
          Client VMs (Jenkins agents) are syncing from a P4D Commit server on 2017.2.1650199.
          P4V is not installed on the client VMs
          Client VMs are an assortment of Windows Server 2016 (8-core, 32GB RAM) and Mac Mojave (4-core, 16GB RAM) VMs

          Let me know if you need any more information

          Show
          kroutley Kurt Routley added a comment - One of our teammates is seeing this again, although their automation stack is on an older version of the p4 plugin and p4d, but based on the p4java release notes it should have sufficient parallel sync support. They hit the issue where sync would run and report success in automation, however the files were not actually sync'd, and it wasn't resolved until they explicitly set the sync configuration to have parallel sync enabled, but with threads, minimum files, and minimum bytes all set to 0. Environment information: Running Jenkins 2.164.2 with P4 Plugin 1.7.4 (uses p4java 2017.2.1535715) and SCM API Plugin 2.6.3. Client VMs (Jenkins agents) are syncing from a P4D Commit server on 2017.2.1650199. P4V is not installed on the client VMs Client VMs are an assortment of Windows Server 2016 (8-core, 32GB RAM) and Mac Mojave (4-core, 16GB RAM) VMs Let me know if you need any more information

            People

            • Assignee:
              douglasawh Doug Whitfield
              Reporter:
              mpiechotka Maciej Piechotka
            • Votes:
              13 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated: