On Wed, Aug 31, 2016 at 8:27 AM, pallen <[email protected]> wrote: > The serialization seems ok when running remotely on slaves for normal use. > However, I noticed an error in my unit tests when I wrap the job with > assertBuildStatusSuccess(job.scheduleBuild2(0)).
Probably just got lucky. To be safe, use `RestartableJenkinsRule` and prove that your code survives restarts. > The 'p4' Groovy object uses a String, a Workspace (made up of other Strings, > ints and booleans) and a TaskListener. I have double checked the > Serialization of Workspace, perhaps TaskListener is the issue? No, you may not serialize a `TaskListener`. Why do you think you need to? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3D_qWVG3BeMsyLN3B6idawh4KurOrB2D3ZTGezuNL36g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
