[
https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158790#comment-158790
]
Michael Clarke commented on JENKINS-12628:
------------------------------------------
I'd personally rather not have to make system calls (such as chmod) as you're
relying on a *nix system which is more of a barrier than relying on having Java
6. I'd prefer to call Java 6 methods and have a fallback if they're not
available (Kohsuke wrote a blog post on Jenkins doing this a while back:
http://weblogs.java.net/blog/2008/11/14/compiling-jdk6-and-running-jdk5). If we
were to implement such a feature then I'd look to having a user warned that
files would not be set as executable through a console message or even a
warning on the CVS section of the job's config screen. Any thoughts?
> 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
