[JENKINS-13133] "Permission denied" due to wrong file system permissions upon update/checkout.

Currently we are using subversion plugin v1.32 - everything works fine.

But after upgrading to the latest v1.39 we encounter some weird behavior:

Upon SVN update i often see a "permission denied" exception.

(well, update works, but the compiler plugin afterwards reports the "permission denied")

The updated file has not the (chmod 664) permission as supposed to be, it only has execute rights (chmod 001)?!

I dunno when this happens or how to get more SVN logging to narrow this down.

Or what changes from .32 to .39 could be the culprit (svnkit upgrade?)

But reverting back to .32 solves this problem immediately....

---
Originally reported by myron, imported from: "Permission denied" due to wrong file system permissions upon update/checkout.

• status: Open
  
• priority: Major
  
• component(s): subversion-plugin
  
• label(s): exception, permissions, plugin, subversion
  
• resolution: Unresolved
  
• votes: 1
  
• watchers: 3
  
• imported: 20251212-090250
  

Raw content of original issue

Currently we are using subversion plugin v1.32 - everything works fine.

But after upgrading to the latest v1.39 we encounter some weird behavior:


Upon SVN update i often see a "permission denied" exception.

(well, update works, but the compiler plugin afterwards reports the "permission denied")

The updated file has not the (chmod 664) permission as supposed to be, it only has execute rights (chmod 001)?!


I dunno when this happens or how to get more SVN logging to narrow this down.

Or what changes from .32 to .39 could be the culprit (svnkit upgrade?)

But reverting back to .32 solves this problem immediately....

environment

```
Jenkins 1.455 - bunch of plugins

Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)

Java version: 1.6.0_22, vendor: Sun Microsystems Inc.

Default locale: en_US, platform encoding: ISO8859-15

OS name: "sunos", version: "5.10", arch: "sparc", family: "unix"

```