[JENKINS-73986] Set SCRIPT_SPLITTING_TRANSFORMATION as the default behavor or explcitly per pipeline. #1480
Description
As a declarative pipeline developer, I would like to apply SCRIPT_SPLITTING_TRANSFORMATION to specific pipelines, so that I can opt into this behavior on specific pipelines instead of enabling it globally.
It doesn't look like the dreaded MultipleCompilationErrorsException error going away anytime soon and SCRIPT_SPLITTING_TRANSFORMATION seems to mitigate this issue enough that it makes this limitation less a problem.
It's been years since SCRIPT_SPLITTING_TRANSFORMATION was included in Jenkins (even though it's a pretty hidden feature). Is it possible that SCRIPT_SPLITTING_TRANSFORMATION is battle tested enough now to turn it on my default?
Otherwise, is it possible that a way to enable this behavior on our pipeline on a per-pipeline bases? For example, a declaration at the top of the Jenkinsfile before the pipeline{} block or a config option in the Configuration page for the job.
Originally reported by henryborchers, imported from: Set SCRIPT_SPLITTING_TRANSFORMATION as the default behavor or explcitly per pipeline.
- status: Open
- priority: Minor
- component(s): pipeline-model-definition-plugin
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 2025-12-06
Raw content of original issue
As a declarative pipeline developer, I would like to apply SCRIPT_SPLITTING_TRANSFORMATION to specific pipelines, so that I can opt into this behavior on specific pipelines instead of enabling it globally.
It doesn't look like the dreaded MultipleCompilationErrorsException error going away anytime soon and SCRIPT_SPLITTING_TRANSFORMATION seems to mitigate this issue enough that it makes this limitation less a problem.
It's been years since SCRIPT_SPLITTING_TRANSFORMATION was included in Jenkins (even though it's a pretty hidden feature). Is it possible that SCRIPT_SPLITTING_TRANSFORMATION is battle tested enough now to turn it on my default?
Otherwise, is it possible that a way to enable this behavior on our pipeline on a per-pipeline bases? For example, a declaration at the top of the Jenkinsfile before the pipeline{} block or a config option in the Configuration page for the job.