-
-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
file permissions Issue - windows #1878
Comments
@karianna Is there any chance this is caused by the copy permissions changes? It seems to be happening just after the installer has been built (installer job completed ok) |
It could be although that is supposed to copy across as the Jenkins user. Do we have any visibility into what the user/group perms are? |
From copyArtifact: _Recommended usage of Copyartifact Copyartifact tries to copy artifacts preserving file attributes like permissions and symbolic links. Though, it may fail in some situations (like for security issues). It’s highly recommended to pack files to copy into an archive file, using tar command or zip pipeline step, especially when it’s important for you to preserving file attributes or directory structures_ |
Potential duplicate of https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1360 so marking as duplicate but leaving open until verified (#1871 is a potential fix) |
|
#1896 might print out the stacktrace for us |
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk8u/job/jdk8u-windows-x64-openj9-windowsXL/330/console
|
Can we print out the file permissions at that stage owner/group etc. |
#1913 has been reverted since it caused build breaks (#1914). |
@M-Davies Can you trigger a re-run of the builds affected by this please now that the fix is in? |
I would suggest adding "debug" echos() to the groovy in the area we think this is occuring, and re-running repeatedly on a suitable Windows box... |
#1942 is a start of "debug echo" as it must print the full stacktrace and not just the message |
I suspect @andrew-m-leonard fixed this when he increased the job retention as I haven't seen this for a while now. The error message we were getting would make sense as it wouldn't be possible to the file permissions if there was no file to get the permissions from! |
jdk11u-windows-x64-openj9
https://ci.adoptopenjdk.net/view/Failing%20Builds/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-windows-x64-openj9/630/console
Execution error: Unable to get file permissions
The text was updated successfully, but these errors were encountered: