[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman reopened an issue Jenkins / JENKINS-56500 Declarative pipeline restricted in code size Change By: Liam Newman Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22912.1588797000841%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~mbrunton27] Thanks for trying that out. So at least we know the feature flag is doing something. I just found out the shared library method limitation this week. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22899.1588796940495%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~mbrunton27] Thanks for trying that out. So at least we know the feature flag is doing something. I just found out the shared library method limitation this week , due to help from part out this week . Would you be willing to share your Jenkinsfile? The last one you mentioned that still gets the error. It would also be useful to me to see the one before this - where your pipeline is in a shared library method. For this one, I only need the Jenkinsfile and the groovy file with the shared library method containing your pipeline directive. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22895.1588796880715%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Matthew Brunton I just found out the shared library method limitation this week, due to help from part out this week. Would you be willing to share your Jenkinsfile? The last one you mentioned that still gets the error. It would also be useful to me to see the one before this - where your pipeline is in a shared library method. For this one, I only need the Jenkinsfile and the groovy file with the shared library method containing your pipeline directive. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22871.1588796700557%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Matthew Brunton edited a comment on JENKINS-56500
Re: Declarative pipeline restricted in code size
I ran some tests with a fresh bare-bones script and a fresh Jenkins, both with and without the feature flag. With the flag on, I do indeed get a few more stages before I hit the error.This is a typical stage, and I'm able to get 27 in parallel without the flag. With the flag, I can get somewhere between 30 and 35 stages. {code:java}def call(){ pipeline { agent any stages{ stage('Build') { parallel {...stage('Parallel Stage 35'){ when {_expression_ {true}}stages { stage('35-A'){when { anyOf{ _expression_ { true } not { _expression_ { true } }} } steps{ testMethod('TEST') } } stage('35-B') { options { timeout(time: 1, unit: 'HOURS') }when { anyOf { _expression_ { true } not { _expression_ { true } } } } steps { testMethod('TEST') } } } }{code}The call to testMethod is just another file under vars:{code:java}// vars/testMethod.groovydef call(String testInput){def testVariable}{code} I get a similar result when I move the pipeline into the Jenkinsfile
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Matthew Brunton commented on JENKINS-56500
Re: Declarative pipeline restricted in code size
I ran some tests with a fresh bare-bones script and a fresh Jenkins, both with and without the feature flag. With the flag on, I do indeed get a few more stages before I hit the error. This is a typical stage, and I'm able to get 27 in parallel without the flag. With the flag, I can get somewhere between 30 and 35 stages.
def call()
{
pipeline
{
agent any
stages
{
stage('Build')
{
parallel
{
...
stage('Parallel Stage 35')
{
when {_expression_ {true}}
stages {
stage('35-A')
{
when
{
anyOf
{
_expression_ { true }
not { _expression_ { true } }
}
}
steps
{
testMethod('TEST')
}
}
stage('35-B')
{
options { timeout(time: 1, unit: 'HOURS') }
when
{
anyOf
{
_expression_ { true }
not { _expression_ { true } }
}
}
steps
{
testMethod('TEST')
}
}
}
}
The call to testMethod is just another file under vars:
// vars/testMethod.groovy
def call(String testInput)
{
def testVariable
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Matthew Brunton commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Liam Newman Yes, I have the feature flag turned on. I also got rid of all def variables outside of the pipeline directive, and I even got rid of all script blocks inside just in case. We do run inside a shared library method, however. Our pipeline is version controlled separately. I see now that this could be the reason why the feature flag workaround isn't working. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22585.1588768800345%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Matthew Brunton edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~bitwiseman]Yes, I have the feature flag turned on. I also got rid of all def variables outside of the pipeline directive, and I even got rid of all script blocks inside just in case.We do run inside a shared library method, however. Our pipeline is version controlled separately. I see now that this could be the reason why the feature flag workaround isn't working. I tried copying the pipeline directive into the Jenkinsfile so the only thing outside of the pipeline is the " @ Library ( ) _ " . I still get the error. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22649.1588772580396%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-56500
Declarative pipeline restricted in code size
Change By:
Liam Newman
{quote}There is partial fix for this in pipeline-model-definition-plugin v1.4.0 and later . Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting a JVM property (either on the command-line or in Jenkins script console):{{org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true }}As noted, this still works best with a Jenkinsfile with {{pipeline}} directive as the only root item in the file. This workaround also works to some extent for pipelines using `def` variables before the {{pipeline}} directive , but not nearly as well. This also workaround generally does not NOT work if the {{pipeline}} directive inside a shared library method. If this is a scenario you want, please come join the pipeline authoring SIG and we can discuss. Please give it a try and provide feedback. {quote}When working with a declarative pipeline script, we run into an error "Method Code too large".This seems to happen when the code between 'pipeline{}' is more than a specific size. I'm creating this issue for this component following the suggestion of Jesse Glick at the issue 37984I've attached a declarative pipeline script that reproduces the issue.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Matthew Brunton Have you tried the feature flag? (See description for note) Do you have any def variables before (or after) your pipeline directive in your Jenkinsfile? Is your pipeline directive inside a shared library method? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22269.1588718161200%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-56500
Declarative pipeline restricted in code size
Change By:
Liam Newman
{quote}There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting a JVM property (either on the command-line or in Jenkins script console):{{org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true }}As noted, this still works to some extent for pipelines using `def` variables, but not nearly as well. This also generally does not work if the {{ pipeline}} directive inside a shared library method. If this is a scenario you want, please come join the pipeline authoring SIG and we can discuss. Please give it a try and provide feedback. {quote}When working with a declarative pipeline script, we run into an error "Method Code too large".This seems to happen when the code between 'pipeline{}' is more than a specific size. I'm creating this issue for this component following the suggestion of Jesse Glick at the issue 37984I've attached a declarative pipeline script that reproduces the issue.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-56500
Declarative pipeline restricted in code size
Change By:
Liam Newman
{quote}There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting a JVM property (either on the command-line or in Jenkins script console):{{org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true }}As noted, this still works to some extent for pipelines using `def` variables, but not nearly as well. This also does not work if the {{ Please give it a try and provide feedback. {quote} When working with a declarative pipeline script, we run into an error "Method Code too large".This seems to happen when the code between 'pipeline{}' is more than a specific size. I'm creating this issue for this component following the suggestion of Jesse Glick at the issue 37984I've attached a declarative pipeline script that reproduces the issue.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Matthew Brunton commented on JENKINS-56500
Re: Declarative pipeline restricted in code size
Liam Newman We have also been running into the method code too large. I was able to get a workaround by switching to a hybrid scripted/declarative, but have been trying various things to get back to declarative. I've tried various methods, including having everything under vars, a mixture of vars and src, and playing around with the various classes we have. Eventually I commented out chunks of code until the pipeline stopped giving "method code too large" and then started adding stuff back. I think I've narrowed it down to the "when {}" stage conditionals. I'm currently using 25 parallel stages (each one has 2 stages, and they are skeletal because of my commented out code) and I've changed all the conditionals to "when { _expression_ {true} }". Some of our conditionals use anyOf {} and not {}, but I set everything to true in order to rule out the expressions themselves. Without the conditionals, there is no "method code too large" error. When I add back the conditionals, the error returns.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22181.1588709700393%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size M McGrath There are reasons to move to Scripted but this is not one of them. In fact, this issue is a reason not to move to scripted. This error can occur in declarative or scripted, but I have no ability to automatically work around it scripted. Perhaps we can try this. Take the Jenkinsfile attached to this issue and try to run it on your Jenkins (without the JVM property). Make sure it encounters the error. Do what you've done before to turn on the fix. Make sure that after that the attached Jenkinsfile does not report the error. That way we can at least be sure that the fix is active on your system. "Templated pipelines with each stage broken out into global vars." - This doesn't sound like Declarative, but maybe I'm not understanding what you're meaning. Can you at least provide an example of what your pipeline looks like (even if you can show your actual pipeline)? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.10737.1576626000497%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title M McGrath edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~bitwiseman] Still hitting this size limit issue with declarative with everything broken out into shared libraries.My code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. At this point i'm starting to test breaking logic out into classes /scr, and a move to scripted pipelines. Im vey techie when it come to how jenkins compiles declarative apart from the 64K size limit. We really liked alot of what declarative pipelines offer, but the file size issue is a pain.Is a move to scripted the right option? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.10590.1576599360922%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title M McGrath edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~bitwiseman] Still hitting this size limit issue with declarative with everything broken out into shared libraries.My code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. At this point i'm starting to test breaking logic out into classes /scr, and a move to scripted pipelines. Im not fully sure vey techie when it come to how the jenkins compiles declarative apart from the 64K size limit. We really liked alot of what declarative pipelines offer, but the file size issue is a pain.Is a move to scripted the right option? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.10577.1576599300404%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title M McGrath commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Liam Newman Still hitting this size limit issue with declarative with everything broken out into shared libraries. My code is predominantly in /vars. Templated pipelines with each stage broken out into global vars. Jenkinsfile passes pipeline params. At this point i'm starting to test breaking logic out into classes /scr, and a move to scripted pipelines. Im not fully sure how the jenkins compiles declarative apart from the 64K size limit. We really liked alot of what declarative pipelines offer, but the file size issue is a pain. Is a move to scripted the right option? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.9764.1576589881612%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size I'm on vacation for the next week. When I get back I'll add a patch to log when this feature is turned on. Maybe some debug information about what it is doing. There should not be a need for further workarounds. How big is your pipeline? Would you be willing to share it with me for debugging? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.3942.1575986040567%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title M McGrath edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~bitwiseman]Updated plugin, removed any def vars, set JVM property on script console.I am still encountering "method too large" on a test job.Reaching this issue on a shared library approach as well, where we have stripped everything out into vars / global methods . Work arounds? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.3884.1575984540404%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Michael McGrath commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Liam Newman Updated plugin, removed any def vars, set JVM property on script console. I am still encountering "method too large" on a test job. Reaching this issue on a shared library approach as well, where we have stripped everything out into vars. Work arounds? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.3872.1575984420723%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size efo plo Yes, even with the "def" variables, it was able to run the example without encountering "method too large". Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.9534.1572979260427%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title efo plo commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Thanks Liam Newman. With your fix, can the attachment be compiled and run? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.9061.1572940140473%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman updated JENKINS-56500 Jenkins / JENKINS-56500 Declarative pipeline restricted in code size Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8769.1572906720810%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman edited a comment on JENKINS-56500
Re: Declarative pipeline restricted in code size
There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting the a JVM property \ (either on the command-line or in Jenkins script console): { { org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true }. }} As noted, this still works to some extent for pipelines using `def` variables, but not as well. Please give it a try and provide feedback.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8700.1572906661865%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman commented on JENKINS-56500
Re: Declarative pipeline restricted in code size
There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting the property {org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true}. As noted, this still works to some extent for pipelines using `def` variables, but not as well. Please give it a try and provide feedback.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8680.1572906540276%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman updated JENKINS-56500 Jenkins / JENKINS-56500 Declarative pipeline restricted in code size Change By: Liam Newman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8669.1572906241365%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman started work on JENKINS-56500 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.8667.1572906241340%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Wim Gaethofs commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Thanks for looking into this issue. I'm glad to hear there is progress in fixing the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.17964.1571819040670%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman commented on JENKINS-56500
Re: Declarative pipeline restricted in code size
This PR will address this issue for scripts that do not use "def" variables before the "pipeline {}" block. https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/355 Your example uses defs so it would still not be fixed. Still, this is progress.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.15565.1571794294526%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-56500 Declarative pipeline restricted in code size Change By: Liam Newman Assignee: Andrew Bayer Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.13648.1571794020433%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title efo plo updated an issue Jenkins / JENKINS-56500 Declarative pipeline restricted in code size Change By: efo plo Summary: Declerative Declarative pipeline restricted in code size Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.5892.1568792162364%40Atlassian.JIRA.
