[
https://issues.jenkins-ci.org/browse/JENKINS-13161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160497#comment-160497
]
Michael Clarke commented on JENKINS-13161:
------------------------------------------
This seems to be being caused by us setting file permission straight after we
create the file but before we write to it. In the situation where the file is
read only, we're clearing the read-only, then setting it again before trying to
write to the file.
Moving the executable/read-only check to after file write should fix this,
although I should remove the duplication of work at some point.
> cvs plugin 2.x fails to update readonly checked out files
> ---------------------------------------------------------
>
> Key: JENKINS-13161
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13161
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: jenkins 1.456, cvs plugin 2.1, java 1.6.0-31
> Reporter: Alex Lehmann
> Priority: Minor
>
> I found a migration issue when switching from cvs-plugin 1.6 to 2.x.
> The regular cvs client support checking out all files readonly to facilitate
> cvs edit/unedit and watchers, apparently this is not supported by the
> netbeans cvsclient.
> If a job was checked out with the old version of the plugin (1.x), updating
> the workspace fails due to
> java.io.FileNotFoundException: some_filename (Permission denied)
> This is not a big issue since the file permissions can be changed with find,
> nevertheless maybe it is possible to change the file handling to change write
> permissions before trying to overwrite the files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
