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

Amir Isfy commented on JENKINS-13227:
-------------------------------------

Here is what happens when I tried it on multiple slaves (Win and Linux):

- I commit a dummy change to the branch.
- Let the project kick off with an SCM poll, as well as I manually triggering 
it on another slave.
- Cleaned out the workspaces, so this is a clean checkout.
- The checkout by the Master goes fine. 
- There is no 'computing changelog' stage.
- The matrix builds are initiated an in both instances I get: 

16:00:58  hudson.util.IOException2: remote file operation failed: 
<workspace_location> at hudson.remoting.Channel@28509953:<slave_name>
16:00:58        at hudson.FilePath.act(FilePath.java:828)
16:00:58        at hudson.FilePath.act(FilePath.java:814)
16:00:58        at hudson.scm.CVSSCM.perform(CVSSCM.java:877)
16:00:58        at hudson.scm.CVSSCM.checkout(CVSSCM.java:808)
16:00:58        at 
hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
16:00:58        at 
hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:586)
16:00:58        at 
hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475)
16:00:58        at hudson.model.Run.run(Run.java:1434)
16:00:58        at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
16:00:58        at 
hudson.model.ResourceController.execute(ResourceController.java:88)
16:00:58        at hudson.model.Executor.run(Executor.java:239)
16:00:58  Caused by: java.io.IOException: Unable to serialize 
hudson.FilePath$FileCallableWrapper@30f3caf4
16:00:58        at hudson.remoting.UserRequest.serialize(UserRequest.java:166)
16:00:58        at hudson.remoting.UserRequest.<init>(UserRequest.java:62)
16:00:58        at hudson.remoting.Channel.call(Channel.java:645)
16:00:58        at hudson.FilePath.act(FilePath.java:821)
16:00:58        ... 10 more
16:00:58  Caused by: java.io.NotSerializableException: 
hudson.scm.CvsRepositoryItem
16:00:58        at 
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180)
16:00:58        at 
java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1362)
16:00:58        at 
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1170)
16:00:58        at 
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
16:00:58        at 
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
16:00:58        at 
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
16:00:58        at 
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
16:00:58        at 
java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1362)
16:00:58        at 
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1170)
16:00:58        at 
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
16:00:58        at 
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
16:00:58        at 
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
16:00:58        at 
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
16:00:58        at 
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
16:00:58        at 
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
16:00:58        at 
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
16:00:58        at 
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
16:00:58        at 
java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
16:00:58        at 
java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
16:00:58        at 
java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
16:00:58        at 
java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
16:00:58        at 
java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346)
16:00:58        at hudson.remoting.UserRequest._serialize(UserRequest.java:155)
16:00:58        at hudson.remoting.UserRequest.serialize(UserRequest.java:164)
16:00:58        ... 13 more

After the failure, the build number says: No changes.
                
> CVS plugin 2.1 does not detect changes
> --------------------------------------
>
>                 Key: JENKINS-13227
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13227
>             Project: Jenkins
>          Issue Type: Bug
>          Components: cvs
>            Reporter: Guillaume Bilodeau
>            Assignee: Michael Clarke
>            Priority: Critical
>              Labels: cvs
>         Attachments: rlog.txt
>
>
> As presented in the user group: 
> https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-users/Dvv0I3FBNW4
> We've been running Jenkins 1.451 and 1.454 on Windows XP against a CVS 
> repository for a few weeks now, without any problems. The CVS plugin (v1.6) 
> was using the local cvsnt install.
> We've since upgraded the CVS plugin to version 2.1 (by manually pinning the 
> plugin) and since then, CVS changes are not detected. The CVS polling log is 
> triggered properly, tons of "cvs rlog" instructions are sent, but at the end 
> "No changes" is displayed.
> Using CVS plugin 1.6 the cvs polling command looked like this (executed at 
> 5:26:21 PM EDT):
> cvs -q -z3 -n update -PdC -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 
> "Thursday, March 22, 2012 9:26:21 PM UTC"
> Using CVS plugin 2.1, the last cvs checkout command looked like this 
> (executed at 11:56:16 AM EDT):
> cvs checkout -P -r d-chg00014229_op_brc_preimp-op-2012-02-27 -D 23 Mar 2012 
> 11:56:16 EDT -d portailInt portailInt
> We're in Montreal, so Eastern Time Zone with Daylight Saving Time in effect.

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