[ 
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

        

Reply via email to