On Thursday, November 17, 2016 at 12:39:26 PM UTC-8, Daniel Beck wrote: > > > > On 17.11.2016, at 17:19, David Karr <[email protected] <javascript:>> > wrote: > > > > What I am unable to find any information on is what exactly a "pipeline > step" actually means. > > Everything you'll find in the snippet generator. >
Ok. I don't think I saw that clearly stated in the other sources I found. As "echo" is one of the pipeline steps, I would guess that "println" does exactly the same thing, but that doesn't appear to be a pipeline step. Is that true? Although I now understand what the limitation is, this still doesn't help my current problem. As can be seen from my example, it is aborting on something that doesn't appear to be a pipeline step (unless "println" is a pipeline step). The line before that "println" that it's not hitting is a "collection.get()" expression, which I'm pretty sure is not a pipeline step. > > I also have a feeling that the "@NonCPS"-state doesn't apply > "lexically", but "dynamically". In other words, if I'm in a @NonCPS > method, and I call a non-@NonCPS method, that method is still effectively > @NonCPS. > > Yes. (Otherwise what I wrote would be trivial to work around and wouldn't > matter at all…) > > -- 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/e4d06a26-fa77-453e-b386-ec584d41f740%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
