[GRADLE-3137] Copy/Sync task from or into a Samba/CIFS network share does not work on a Linux maschine? Created: 20/Jul/14 Updated: 10/Feb/17 Resolved: 10/Feb/17 |
|
Status: | Resolved |
Project: | Gradle |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Task | ||
Reporter: | Gradle Forums | Assignee: | Unassigned |
Resolution: | Won't Fix | Votes: | 2 |
Description |
Hi everybody! Following sync (copy) task: task deploy(type: Sync) { When I execute the gradle task on a Windows machine there are no problems. On a linux machine I got following error: FAILURE: Build failed with an exception.
What is the best procedure to sync or copy with a Samba/CIFS network share on a linux machine? Is it possible to keep the same directory path for both platforms windows and linux? Regards, |
Comments |
Comment by Gradle Forums [ 20/Jul/14 ] |
On Linux you'll have to mount the network share, and then reference the mount point. I doubt you can have one path that works for both platforms. |
Comment by Gradle Forums [ 20/Jul/14 ] |
I have the windows share mounted on linux, but then the gradle build fails when it tries to set the file mode on the target file: Caused by: java.io.IOException: Failed to set file permissions 420 on file targetFile.zip. errno: 1 Build runs on a linux but the target file is on a mounted windows share. |
Comment by Gradle Forums [ 20/Jul/14 ] |
Previous error was using version 1.4. Caused by: net.rubygrapefruit.platform.NativeException: Could not set UNIX mode on targeFile.zip: could not chmod file (errno 1) |
Comment by Benjamin Muschko [ 15/Nov/16 ] |
As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub. We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to. Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:
We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle! |
Comment by Benjamin Muschko [ 10/Feb/17 ] |
Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved. |