[
https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158792#comment-158792
]
Alex Lehmann commented on JENKINS-12628:
----------------------------------------
chmod isn't necessary on windows anyway, if you have a wrapper the checks if
the target system is unix-like and run chmod or do nothing otherwise
if it is possible to check for java5/java6, this could be used before if
possible, something like this
{code}
if(isUnix) {
if(isJava6) {
File.setExecutable();
} else {
System.execute("chmod ...");
}
} else {
warn("ignoring execute permission for ...");
}
{code}
> Executable file permission not set anymore
> ------------------------------------------
>
> Key: JENKINS-12628
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12628
> Project: Jenkins
> Issue Type: Bug
> Components: cvs
> Environment: CentOS release 5.7 (affected system, Slave), Windows
> Server 2003 (Master)
> Reporter: Marco Borm
> Fix For: current
>
>
> Updating the cvs plugin from 1.6 to 2.0 breaks all our linux builds, due the
> fact that our compile scripts don't have executable permission bit set
> anymore. The bit is correctly set on the affected files on cvs server side.
> cvs plugin 1.6:
> -rwxrwx--- 1 jenkins jenkins 261 15. Mai 2007 compile.linux.so.release
> cvs plugin 2.0:
> -rw-rw-r-- 1 jenkins jenkins 261 15. Mai 2007 compile.linux.so.release
--
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
