[JIRA] (JENKINS-50541) Pipeline failing - due to java.io.NotSerializableException
Title: Message Title Alexey Vishnaikov commented on JENKINS-50541 Re: Pipeline failing - due to java.io.NotSerializableException Thank you for quick answer. Sometimes it is very hard to understand where problem is located. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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/d/optout.
[JIRA] (JENKINS-50541) Pipeline failing - due to java.io.NotSerializableException
Title: Message Title Andrew Bayer resolved as Not A Defect Oleg is correct - the Pipeline's execution gets serialized, so any attempt to reference/use objects that can't be serialized will lead to errors like this. The solution is to encapsulate your code that refers to unserializable objects inside a method annotated with @NonCPS. You can't run steps inside a method annotated with @NonCPS, and you should make sure that whatever you return from that method is serializable. Jenkins / JENKINS-50541 Pipeline failing - due to java.io.NotSerializableException Change By: Andrew Bayer Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50541) Pipeline failing - due to java.io.NotSerializableException
Title: Message Title Oleg Nenashev commented on JENKINS-50541 Re: Pipeline failing - due to java.io.NotSerializableException You should access run list within NonCPS step. Otherwise Pipeline will be persisting data on the disk Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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/d/optout.
[JIRA] (JENKINS-50541) Pipeline failing - due to java.io.NotSerializableException
Title: Message Title Pradip Sakhavala created an issue Jenkins / JENKINS-50541 Pipeline failing - due to java.io.NotSerializableException Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-04-03 10:07 Environment: Jenkins - 2.73.3 OS - Red Hat Enterprise Linux Server release 7.3 (Maipo) java - jdk1.8.0_60 Priority: Minor Reporter: Pradip Sakhavala I am facing below issue abnormally on different stages of my pipeline in different branches. Sometimes, Build is passed, sometimes It fails with below error on different stages. an exception which occurred: in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@1bc0dd2f in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@66846a22 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@748103ca in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.LoopBlockScopeEnv@8d83000 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@12ab52b6 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@1d673eb0 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@1294d8e0 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@39799cf4 in field com.cloudbees.groovy.cps.Continuable.e in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@46398717 in field org.jenkinsci.plugins.workflow.cps.CpsThread.program in object org.jenkinsci.plugins.workflow.cps.CpsThread@367b33bb in field
