[JIRA] (JENKINS-12628) Executable file permission not set anymore

Marco Borm created JENKINS-12628:
------------------------------------

             Summary: 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158737#comment-158737 ]

Alex Lehmann commented on JENKINS-12628:
----------------------------------------

I wonder if that is an issue with the pure java cvs client, since Java doesn't handle unix permissions properly (or most programs don't before java 7)


               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158738#comment-158738 ]

Michael Clarke commented on JENKINS-12628:
------------------------------------------

The cvs client doesn't do anything with permission just now. It's possible to use File.setExecutable() providing I can work out what response from the server specifies the permission. There is an outstanding Netbeans issues for this which no-one seems to have done any work on (I don't have the details to hand though).
               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158749#comment-158749 ]

Alex Lehmann commented on JENKINS-12628:
----------------------------------------

From what I found in the source code for cvslib, the library doesn't implement unix permissions, so this is outside the scope of the plugin.


               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158765#comment-158765 ]

Alex Lehmann commented on JENKINS-12628:
----------------------------------------

I have to admit that I wasn't aware of the file execute property in java 6, that should be possible to implement (is an issue for the library though I guess).

Jenkins is still supporting Java 5, though I think.


               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158766#comment-158766 ]

Marco Borm commented on JENKINS-12628:
--------------------------------------

I'm a C++, not a Java developer: Maybe a call to chmod could a solution if the java cvslib runs on Java 5?
               

> 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

       

    [ 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

       

    [ 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158792#comment-158792 ]

Alex Lehmann edited comment on JENKINS-12628 at 2/8/12 9:02 PM:
----------------------------------------------------------------

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}

if this is properly wrapped in a method, this will not even look bad in the actual code since that only has to do Wrapper.setExecutable(file);


               
      was (Author: alexlehm):
    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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158928#comment-158928 ]

Alex Lehmann commented on JENKINS-12628:
----------------------------------------

I found a similar function in Jenkins that makes a file writable using shell chmod, jdk6 and even libc chmod, maybe we could use this for changing execute permissions.

take a look at jenkins/core hudson/Util.java#makeWritable(File f)


               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159030#comment-159030 ]

Michael Clarke commented on JENKINS-12628:
------------------------------------------

Unfortunately that method is private and only caters for writeable, not executable. I'd also like to try and get the patches to Cvs client merged into the upstream project which would mean we couldn't add dependencies on the Jenkins core as this would require distributing Jenkins with Netbeans.

Cvs-plugin has been compiled to Java 1.6 since version 1.3 (9 months ago) so it would be safe to make the underlying client use the File.setExecutable() method and compile it at Java 1.6 too. Unless there's any objections to this then I'll use the File methods and have no handling for Java fall back (i.e. users must use Java 1.6 or above).
               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159119#comment-159119 ]

Marco Borm commented on JENKINS-12628:
--------------------------------------

For me, Java 1.6 is ok.
I am wondering if nobody else checks out executable scripts on Linux/Unix and has broken build service with the new release.
               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159121#comment-159121 ]

Alex Lehmann commented on JENKINS-12628:
----------------------------------------

I guess most cvs users may not updated to 2.0

currently this is notified by the update center but the jenkins distribution still contains 1.6


               

> 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159121#comment-159121 ]

Alex Lehmann edited comment on JENKINS-12628 at 2/15/12 3:25 PM:
-----------------------------------------------------------------

I guess most cvs users may not updated to 2.0

currently this is notified by the update center but the jenkins distribution still contains 1.6

(java 1.6 is fine with me as well, I started using Tomcat 7 a while ago, that is Java 1.6 anyway)

               
      was (Author: alexlehm):
    I guess most cvs users may not updated to 2.0

currently this is notified by the update center but the jenkins distribution still contains 1.6


                 

> 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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Clarke reassigned JENKINS-12628:
----------------------------------------

    Assignee: Michael Clarke
   

> 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
>            Assignee: Michael Clarke
>             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

       

     [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on JENKINS-12628 started by Michael Clarke.

> 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
>            Assignee: Michael Clarke
>             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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159130#comment-159130 ]

SCM/JIRA link daemon commented on JENKINS-12628:
------------------------------------------------

Code changed in jenkins
User: Michael Clarke
Path:
 pom.xml
http://jenkins-ci.org/commit/cvs-plugin/50d22a4953688f2ead47eba4f3608de63fef5a2c
Log:
  [FIXED JENKINS-12628] - Upgrading to CVS client with permission support
[FIXED JENKINS-12599] - Upgrading to CVS client with ext support



               

> 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
>            Assignee: Michael Clarke
>             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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159133#comment-159133 ]

dogfood commented on JENKINS-12628:
-----------------------------------

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_cvs #9|http://ci.jenkins-ci.org/job/plugins_cvs/9/]
     [FIXED JENKINS-12628] - Upgrading to CVS client with permission support (Revision 50d22a4953688f2ead47eba4f3608de63fef5a2c)

     Result = SUCCESS
michael.m.clarke :
Files :
* pom.xml

               

> 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
>            Assignee: Michael Clarke
>             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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159371#comment-159371 ]

Fred G commented on JENKINS-12628:
----------------------------------

Here is the stacktrace with Java 1.5 on a Solaris Sparc machine (tested with 2.1-snapshot release):

{code}
hudson.util.IOException2: remote file operation failed: <matrix job label>
at hudson.remoting.Channel@1273510:Solaris_Sparc_Slave
   at hudson.FilePath.act(FilePath.java:780)
   at hudson.FilePath.act(FilePath.java:766)
   at hudson.scm.CVSSCM.perform(CVSSCM.java:871)
   at hudson.scm.CVSSCM.checkout(CVSSCM.java:803)
   at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
   at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:573)
   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462)
   at hudson.model.Run.run(Run.java:1404)
   at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)
Caused by: java.io.IOException: Remote call on Solaris_Sparc_Slave failed
   at hudson.remoting.Channel.call(Channel.java:690)
   at hudson.FilePath.act(FilePath.java:773)
   ... 10 more
Caused by: java.lang.NoSuchMethodError: java.io.File.setReadable(ZZ)Z
   at org.netbeans.lib.cvsclient.file.DefaultFileHandler.setFileMode(DefaultFileHandler.java:589)
   at org.netbeans.lib.cvsclient.file.DefaultFileHandler.writeAndPostProcessTextFile(DefaultFileHandler.java:341)
   at org.netbeans.lib.cvsclient.file.DefaultFileHandler.writeTextFile(DefaultFileHandler.java:303)
   at org.netbeans.lib.cvsclient.response.UpdatedResponse.process(UpdatedResponse.java:178)
   at org.netbeans.lib.cvsclient.response.CreatedResponse.process(CreatedResponse.java:54)
   at org.netbeans.lib.cvsclient.Client.handleResponse(Client.java:648)
   at org.netbeans.lib.cvsclient.Client.processRequests(Client.java:598)
   at org.netbeans.lib.cvsclient.command.checkout.CheckoutCommand.postExpansionExecute(CheckoutCommand.java:462)
   at org.netbeans.lib.cvsclient.command.checkout.CheckoutCommand.execute(CheckoutCommand.java:355)
   at org.netbeans.lib.cvsclient.Client.executeCommand(Client.java:710)
   at hudson.scm.CVSSCM$2.invoke(CVSSCM.java:891)
   at hudson.scm.CVSSCM$2.invoke(CVSSCM.java:871)
   at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2045)
   at hudson.remoting.UserRequest.perform(UserRequest.java:118)
   at hudson.remoting.UserRequest.perform(UserRequest.java:48)
   at hudson.remoting.Request$2.run(Request.java:287)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
   at java.util.concurrent.FutureTask.run(FutureTask.java:123)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
   at java.lang.Thread.run(Thread.java:595)
{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
>            Assignee: Michael Clarke
>             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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159377#comment-159377 ]

Alex Lehmann commented on JENKINS-12628:
----------------------------------------

this needs to be in a try block that catches NoSuchMethodError similar to the permission method in hudson.utils


               

> 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
>            Assignee: Michael Clarke
>             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