tkleiber
I'm glad you were able to figure out the problem.

tkleibersodul moskovych jmcclain
How is the feature behaving for you? Do you have any feedback, comments, observations? I'm trying to evaluate it's readiness for wider use.

How is the feature behaving for you? Do you have any feedback, comments, observations?

bitwiseman For reference, initially one of my larger pipelines stopped working, so I tried the 

org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true

workaround, however it just resulted in a different message about needing to set 

SCRIPT_SPLITTING_ALLOW_LOCAL_VARIABLES=true

in order to use variables defined outside of my pipeline, and even then I still needed to add "import groovy.transform.Field" and "@Field" declarations to my variables and the "env." prefix seemed to stop being recognized by Jenkins for defining environment variables within my pipeline, etc.

Eventually I just moved some of my pipeline stages to a downstream helper job to get the overall pipeline working again, which I'm guessing is the recommended approach anyways rather than manually changing the experimental settings for SCRIPT_SPLITTING_TRANSFORMATION and SCRIPT_SPLITTING_ALLOW_LOCAL_VARIABLES to true.

I'd say it definitely seems to be a bit of a breaking change, but if you think the optimization is worth it then I don't really mind. I feel like the error message could be a bit more intuitive though, maybe something like:

"Your declarative pipeline code is [x]kb which exceeds Java's maximum bytecode size of 64kb and therefore can't be parsed by Jenkins. Consider moving some stages to downstream pipelines or splitting your pipeline into multiple smaller pipelines to reduce your code size to satisfy Java's 64kb limit. Alternately, set org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true as a workaround. See Jenkins-37984 for more details."

> bitwiseman: How is the feature behaving for you? Do you have any feedback, comments, observations?

With this feature our main declarative multi branch pipeline works only with the SCRIPT_SPLITTING_TRANSFORMATION feature, without it we would have to go to back to classic up-/down-stream approach. We don't use variables outside of the pipeline at the moment. All other pipelines are small enough.

We use here trunk based development in a monorepo for our main loan application with different backend and frontend technologies. And not all are implemented at till now.

Despite we try to move a lot of logic to pipeline libraries there remains a lot of stages because of when conditions depending on branching model and repository names (eg. for testing jenkins staging). Furtermore we need different pipeline stages for environments like development, test and production or for different controllers for building on different operating systems.

One thing we miss at the moment is better parallel support as other systems like UC4 have. Eg. parallel in parallel and the corresponding visualization in blue ocean.

> bitwiseman: How is the feature behaving for you? Do you have any feedback, comments, observations?

We are not using the SCRIPT_SPLITTING_TRANSFORMATION set (by default it false, right?).

Our pipelines mostly use methods/functions from Jenkins Shared library and
all pipelines contains some global variables before pipeline block (variables with some groovy logic, which used in more than 2 stages, or should be defined as global).
The example of pipeline you may take from this issue description: JENKINS-64846

Pipelines are separated from functions, so - no pipeline blocks in call functions for shared library, like it was shown here: JENKINS-64846?focusedCommentId=407258

bitwiseman, I know, this is beta, but is there any documentation available for description of flags and behavior of pipelines? It would be good to have examples without diving in the plugin source code. Especially with our approach of using groovy outside pipeline block.

As I want to test a specific library branch I try to use follwing notation: 

@Library('shared-libraries@feature/test-shared-library') _

pipeline {
  // long pipeline here
}

Therefore I tried to use following properties combined:

-Dorg.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true -Dorg.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_ALLOW_LOCAL_VARIABLES=true 

But as soon as I add the second parameter, the first will not work anymore. Is this the intended behavior? So I cannot use local libraries in big pipelines? Or do I have to do this in another way?

Jenkins 2.387.1 on SLES 12.5.