-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins ver. 2.60.3
Filesystem SCM Plugin 2.0
Steps to reproduce:
- Have a Jenkins job that uses the FSSCM plugin to copy from the file system into the workspace.
- Execute the job at least once.
- Change the modifiers on one of the files in the origin location, e.g. change the x (executable) bit from off to on (e.g. chmod +x filename)
- Re-execute the job.
Expected result:
- The modifier bit changes also in the checked-out version of the respective file.
Actual result:
The modifier bit does not change.
- links to
I checked the code and yes you are right this will happen.
Why is it happening: The code checks for modification dates, but changing file Permissions / modifiers does not change the date.
File permissions seem to be be a troublesome topic, especially in Windows. So any code modification to achieve the desired behavior, will lead, in my opinion to more bug reports. Or to an exclusion list like File Permissions will be checked but, .... under windows x with Java y it might not work.
Maybe this topic should be rested as a known bug and be documented.
Lets ask oleg_nenashev. I could implement it if he approves the topic to be worthwhile implementing.