Change By: Mark Waite (07/Mar/13 9:55 PM)
Description: Using the git plugin to publish a merged change to a central repository previously was successful from either the master node or a slave agent.  With the 1.2.0 version of the git plugin it is no longer able to push changes to the central repository after they have merged and are successfully built on the slave.

The stack trace reports:

Commencing build of Revision 363396d76a09a12a2f4b5d94fb4e9981e05ad4a9 (origin/proposals)
hudson.util.IOException2: remote file operation failed: /var/lib/jenkins/mwaite6-slave/workspace/merge-proposals at hudson.remoting.Channel@4a6ecaf9:fc-agile-2011
at hudson.FilePath.act(FilePath.java:848)
at hudson.FilePath.act(FilePath.java:834)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1133)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1256)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495)
at hudson.model.Run.execute(Run.java:1502)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@7c0a37f8
at hudson.remoting.UserRequest.serialize(UserRequest.java:166)
at hudson.remoting.UserRequest.<init>(UserRequest.java:62)
at hudson.remoting.Channel.call(Channel.java:671)
at hudson.FilePath.act(FilePath.java:841)
... 10 more
Caused by: java.io.NotSerializableException: hudson.model.FreeStyleBuild
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346)
at hudson.remoting.UserRequest._serialize(UserRequest.java:155)
at hudson.remoting.UserRequest.serialize(UserRequest.java:164)
... 13 more

Steps to recreate the problem:

 - configure a Git repository into which the Jenkins user can push changes
 - create a "master" branch and a "proposals" branch on the Git repository
 - define a Jenkins job which clones the Git repository with ssh protocol
 -
 restrict the job to execute on any node except master node ("!master")
 -
 configure the Jenkins job git plugin to merge from "*/proposals" and "*/master" to "master-proposals"
 -
 configure  restrict  the  Jenkins  job to  run  execute  on  a slave agent  any node except master node  ( not "!  master " )
 - define a post build action to push the resulting merge to the origin/master branch
 - Submit a change to the central git repository on the "proposals" branch
 - Run the Jenkins job to confirm it will combine the master and proposals branches
 - Confirm the Jenkins job fails to push the combined change
   = Serialization exception between master and slave.

Refer to merge-proposals.xml for the job definition I used in my tests.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to