On Saturday, December 20, 2014 11:27:11 PM UTC-5, Kenneth Baltrinic wrote: > > all classes get serialized by Jenkins-workflow's state-saving mechanism > that allows for resuming inflight workflows >
Yes. > state to be created/managed on the master node yet replicated to slave > nodes for execution > Workflows run entirely on the master, never slaves. Steps like ‘sh’ may fork processes on slaves and so on, but the Groovy itself remains local. I am curious if there is any documentation around the implications and > limitation that this need to be serializable places on classes. > A little: https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md#serialization-of-local-variables Which gets me back to my current dilemma. Again this may be more of a > groovy question > I am afraid I did not follow what your actual question here was. (Kohsuke might be better placed to answer it anyway.) -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/3bd15356-b635-49e3-8b5d-fb300586cdd7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
