We’ve run into the “method to large” errors few times in the last couple years, and have been working to reduce the size of the the pipeline using a shared library. We’re also trying to refactor parts of the pipeline to simplify them. The "method too large’ error is always there in the back of the mind, though, and we’d really like to figure out a way to track the compiled size of a Jenkins file. Is that possible?
This old article talks about the source of the exception and how to deal with it…
As for determining the size yourself? I dunno. I used shared pipelines from the beginning so I’ve never run into the issue myself.
Yeah, my googling has turned up anything, thank you for the response though!