-
Bug
-
Resolution: Fixed
-
Minor
-
OS: RHEL 6
Jenkins: 2.93
ThinBackup: 1.9
After upgrading to Jenkins 2.93, ThinBackup sets the permissions of installedPlugins.xml to 600. Previously, the permission were 644, matching the original file.
If I watch the permissions as a backup is running, the permissions start as 644, but change to 600 by the time the backup completes.
The dnusbaum user on IRC recommended I create this issue.
EDIT: This issue was discovered when automation attempts to copy the backups files off of the server as non jenkins user. I assume since the permissions of the backups are different than JENKINS_HOME, that restoring would fail. I have not had a chance to test this theory.
- relates to
-
JENKINS-34855 AtomicFileWriter isn't Atomic
-
- Resolved
-
-
JENKINS-36088 Use NIO rather than JNR whenever possible
-
- Resolved
-
- links to
[JENKINS-48407] Permission issue after upgrade to 2.93
Link |
New:
This issue relates to |
Thanks for creating the ticket. Can you confirm whether you mean that the permissions of installedPlugins.xml are incorrect in the file that is in the backup archive, or that the permissions of installedPlugins.xml in JENKINS_HOME is changing?
There is a chance that the chmod/mode changes as part of
JENKINS-36088could be causing this, but you said that setting hudson.util.useNativeChmodAndMode=true had no effect? It looks like thinbackup-plugin uses the java.util.zip API, which does not preserve file permissions or use chmod/mode, so I don't think the changes in 2.93 would affect this. We could potentially modify the plugin to use ZipArchiver so that it would preserve permissions, but that doesn't explain why this is a problem now.Are you unzipping the backup somewhere other than when it was working before you upgraded to 2.93? umask settings should affect permissions on the unzipped archive.