We find ourselves struggling with:
org.jenkinsci.plugins.workflow.cps.CpsCompilationErrorsException: startup failed: General error during class generation: Method code too large! I understand that this is due to underlying jvm limitations... My question is "does embedded node scripting such as sh blocks" contribute directly to the method size in any meaningful way or are each of these blocks basically just data off to the side that the script references? In other words is moving this script out of groovy and into standalone script files likely to help? In this particular case it is a scripted pipeline, but we run into this problem with declarative also. On a related note, is there anyway to learn the current 'method size' ? ----------------------------------------------------------------------------------------------------------------------- Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments. ----------------------------------------------------------------------------------------------------------------------- -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/BN8PR03MB50097169F358579BAE29205AAFF50%40BN8PR03MB5009.namprd03.prod.outlook.com.
