Hi,
I see there are many discussions about the pipeline code hit the  "method 
code too large" error.
While the simple answer about how to resolve the problem is to "make the 
pipeline simple", I'm wondering if there is a way to analyze the code to 
get an understanding what kind of code/function/step is contribute to the 
method code size, and how many?

Currently writing the pipeline code is like a guess work. 
Will my next change make it exceed the limit? I don't know and I have to 
try.

Thanks for the help.

-- 
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/14dd4d73-27f2-4e64-a649-705c5c9a249f%40googlegroups.com.

Reply via email to