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....
I also had this problem with subversion plugin v1.39. After a workspace wipeout all files checked out had permissions "---------x" (001).
After upgrading jenkins to 1.467 and plugin 1.40 now all files have the same permission "-rwxrwxr-x" (775) regardless if they had the property set for execution or not.
This however didn't show in all build slaves, only in the master, where i recently changed from java 1.6 to 1.7 and added the flag -d64 in order to use 64-bit data model and allocate more memory for max-heap.
After more testing I got to the conclusion that this problem doesn't occur if the flag "-d64" isn't passed to java starting options.