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

P4 Plugin - Errors when syncing symlinks

    Details

    • Type: Bug
    • Status: In Progress (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: p4-plugin
    • Environment:
    • Similar Issues:

      Description

      After updating from 1.10.0 to 1.10.3 I am seeing the following errors on Windows build slaves:

      15:00:01  ERROR: P4: Task Exception: com.perforce.p4java.exception.P4JavaException: com.perforce.p4java.exception.P4JavaException: hudson.AbortException: P4JAVA: Error(s):
      15:00:01  symlink file <some symlink> can't be sync'd or created with this client program.
      

      Note that we are using a virtual stream. 

       

        Attachments

          Issue Links

            Activity

            Hide
            p4paul Paul Allen added a comment -

            It's possible that the older 1.10.0 release may have left a 'bad' symlink in your workspace with strange permissions.  You may need to use 'administrator' permissions to clean up the file. 

            Windows has a few types of symlinks; the plugin only supports 'symlinks' not 'junctions' JENKINS-57955.

            If it still causes a problem please let me know.

            Show
            p4paul Paul Allen added a comment - It's possible that the older 1.10.0 release may have left a 'bad' symlink in your workspace with strange permissions.  You may need to use 'administrator' permissions to clean up the file.  Windows has a few types of symlinks; the plugin only supports 'symlinks' not 'junctions'  JENKINS-57955 . If it still causes a problem please let me know.
            Hide
            ivtashev Ivan Tashev added a comment - - edited

            Hey Paul Allen, thank you for the responce.

            The error was actually revealed after I did a full wipe and recreate of the workspace (after basically deleting local files and p4 client). I am not sure this is an OS specific issue, as I can sync the files on the same build node with P4V using the same p4 client. 

            Show
            ivtashev Ivan Tashev added a comment - - edited Hey Paul Allen , thank you for the responce. The error was actually revealed after I did a full wipe and recreate of the workspace (after basically deleting local files and p4 client). I am not sure this is an OS specific issue, as I can sync the files on the same build node with P4V using the same p4 client. 
            Hide
            p4karl Karl Wirth added a comment -

            Hi Ivan Tashev - I'd like to ask you for some system specific information so is it OK if I email you directly?

             

            Show
            p4karl Karl Wirth added a comment - Hi Ivan Tashev - I'd like to ask you for some system specific information so is it OK if I email you directly?  

              People

              • Assignee:
                cbopardikar Charusheela Bopardikar
                Reporter:
                ivtashev Ivan Tashev
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: