java.io.IOException

Unable to communicate with perforce. Error in client specification. 'client_validation' validation failed: The LineEnd attribute for this client spec (workspace) does not use the 'share' setting. Correct and re-submit. For Command: p4 -s client -i With Data: =================== Client: hudson_mainline-hudson Owner: qc Description: Created by qc. Root: /root/.hudson/jobs/Perforce_Mainline/workspace/ Options: noallwrite noclobber nocompress unlocked nomodtime normdir SubmitOptions: submitunchanged LineEnd: local View: //depot/silhouette/... //hudson_mainline-hudson/... ===================

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web9

  • via Unknown by willjw1,
  • via Unknown by willjw1,
  • Stack trace

    • java.io.IOException: Unable to communicate with perforce. Error in client specification. 'client_validation' validation failed: The LineEnd attribute for this client spec (workspace) does not use the 'share' setting. Correct and re-submit. For Command: p4 -s client -i With Data: =================== Client: hudson_mainline-hudson Owner: qc Description: Created by qc. Root: /root/.hudson/jobs/Perforce_Mainline/workspace/ Options: noallwrite noclobber nocompress unlocked nomodtime normdir SubmitOptions: submitunchanged LineEnd: local View: //depot/silhouette/... //hudson_mainline-hudson/... =================== at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:368) at hudson.model.AbstractProject.checkout(AbstractProject.java:830) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:314) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:266) at hudson.model.Run.run(Run.java:927) at hudson.model.Build.run(Build.java:112) at hudson.model.ResourceController.execute(ResourceController.java:93) at hudson.model.Executor.run(Executor.java:119)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.