[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Pete McNab commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script This issue is three years old and has never really been addressed with anything other than vague marketing-speak and nothing definitively helpful for people who listened to the screams from Jenkins to migrate to pipelines, only to discover all the limitations. But you can happily pay Cloudbees for enterprise support and more expensive add-ons which still won't solve your problems. Give it up, find another solution. 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.174127.1473169024000.943.1573746361838%40Atlassian.JIRA.
[JIRA] (JENKINS-40460) Null Pointer Exception when polling P4
Title: Message Title Pete McNab created an issue Jenkins / JENKINS-40460 Null Pointer Exception when polling P4 Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Dec/14 10:23 PM Environment: Jenkins 2.19.4 P4 Plugin 1.4.11 Priority: Critical Reporter: Pete McNab I have a pipeline job and when I turned on SCM polling, My P4 Polling log reports an NPE: (some internal strings replaced by <>) Started on Dec 14, 2016 2:08:00 PM P4: Polling on: master with: Found last change 1468074 on client ... p4 client -o + ... p4 info + P4 Task: establishing connection. ... server: perforce:1666 ... node: P4: Polling with range: 1468074,now ... p4 changes ///...@1468074,now + P4: Polling on: master with:jenkins-master---BUILD_NUMBER-- ... p4 client -o jenkins-master---BUILD_NUMBER--___ + ... p4 info + P4 Task: establishing connection. ... server: perforce:1666 ... node: P4 Task: attempt: 1 P4 Task: failed: java.lang.NullPointerException ERROR: polling failed in /var/tmp/workspace// on : P4 Task: failed: java.lang.NullPointerException Done. Took 3.3 sec No changes The jenkins.log reports: Dec 14, 2016 2:13:00 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask SEVERE: P4 Task: attempt: 1 java.lang.NullPointerException at
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Pete McNab commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) I'd add another note that in my opinion in the case where a job does multiple syncs/polls, P4_CHANGELIST should contain a deduplicated list of all the changes detected. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37584) P4 plugin : P4_CHANGELIST not available in workflow (pipeline)
Title: Message Title Pete McNab commented on JENKINS-37584 Re: P4 plugin : P4_CHANGELIST not available in workflow (pipeline) My pipeline has lots of syncs that happen, and I'd also like to see this kind of behavior. Taken a step further though, I'd like to be able to access detected changelists on a per-sync basis. If I use the polling option of the checkout method, I'd want to be able to access the list of detected changelists. Preferably, I'd either be able to specify the target environment variable for each poll, or have it named based on the client name doing the polling. To give more details of my use case, a typical pipeline script would compile multiple targets on multiple platforms. Each target/platform combination can have different sources. I want to be able to skip target/platform combinations if there are no changes to that specific view. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title
Pete McNab created an issue
Jenkins / JENKINS-39652
Add support for polling multiple checkouts with pipeline scripts
Issue Type:
New Feature
Assignee:
Paul Allen
Components:
p4-plugin
Created:
2016/Nov/10 5:52 PM
Environment:
Jenkins 2.19.2, all pipeline-related plugins at latest version, p4-plugin at version 1.4.8
Labels:
pipeline
Priority:
Critical
Reporter:
Pete McNab
We're attempting to run some large pipeline jobs. Each job goes and runs a series of parallel jobs on multiple platforms for multiple targets. When adding the options to include in changelog/polling that are now available:
checkout([
changelog: true,
poll: true,
scm: [
$class: 'PerforceScm',
credential: credential,
...
The job will try to poll for changes. It correctly polls the actual Jenkinsfile, but when it goes to poll for each separate checkout in the pipeline script, it loses track of the previous change it built at and continually triggers a new build. The name of our generated clients is: 'jenkins-$ {NODE_NAME} -$ {JOB_NAME} -$ {BUILD_NUMBER} -' + platform The p4 plugins normally adds a "Description:" field into the client tracking the last change. During my
[JIRA] (JENKINS-39578) Unable to connect to perforce SCM from pipeline script SCM.
Title: Message Title Pete McNab commented on JENKINS-39578 Re: Unable to connect to perforce SCM from pipeline script SCM. Can you provide any more information? You can definitely sync sources from Perforce from pipeline scripts. Include your code and the specific errors you are getting Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Pete McNab commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I made one – I still think this case should be touched on in the Pipeline docs. I don't think searching Jira or StackOverflow is a substitute for documentation Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Pete McNab edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Whoops. Well cancel what I said. When I generated the code with what I intended to be methods I was actually defining closures attached to a variable , and now . When I did it properly as methods it 's happy ok with it.So more specifically, for those of you who find this, what I used to have was:{noformat}stage fooparallel([ ... giant list of maps ...]){noformat}What I changed it to was:{noformat}stage foodef build_foo() { parallel([ ...giant list of maps... ])}build_foo(){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Pete McNab edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Whoops. Well cancel what I said. When I generated the code with what I intended to be methods I was actually defining closures attached to a variable, and now it's happy with it.So more specifically, for those of you who find this, what I used to have was:{noformat}stage fooparallel([ ... giant list of maps ...]){noformat}What I changed it to was:{noformat}stage foodef build_foo() { parallel([ ...giant list of maps... ]) } build_foo(){noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Pete McNab edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Whoops. Well cancel what I said. When I generated the code with what I intended to be methods I was actually defining closures attached to a variable, and now it's happy with it.So more specifically, for those of you who find this, what I used to have was: {noformat} stage fooparallel([ ... giant list of maps ...]) {noformat} What I changed it to was: {noformat} stage foodef build_foo() { parallel([ ...giant list of maps... ])build_foo() {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Pete McNab commented on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Whoops. Well cancel what I said. When I generated the code with what I intended to be methods I was actually defining closures attached to a variable, and now it's happy with it. So more specifically, for those of you who find this, what I used to have was: stage foo parallel([ ... giant list of maps ... ]) What I changed it to was: stage foo def build_foo() { parallel([ ...giant list of maps... ]) build_foo()
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Pete McNab commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Yeah it's kind of puzzling – as part of my testing I had reduced the number of stages significantly. So a version that worked had 4 stages with no methods and it was about 1720 lines. With the full set of stages (27), the number of lines is about 5300 lines. Breaking it up into methods had no method larger than about 450 lines, but it wouldn't run. I also went in and removed the 4 stages that had worked, which put the entire script down to ~3600 lines broken out into methods, and that wouldn't run either. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Pete McNab edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I've run into the same problem. I have a large (200+kb) pipeline script that is generated from our legacy build specification language. My generated code is broken up into stages, with each stage running a potentially large parallel pipeline operation, where each platform of a given target is built.After some googling about the underlying cause, I attempted to break it up by having each stage be defined as a method and calling the method rather than just having all the code in one giant block, but it didn't help. As this will impact a lot of people trying to migrate to the Jenkins pipeline, and may make them throw up their hands due to the error being vague and unhelpful (which I realize is not the fault of Jenkins, but the underlying Java/Groovy architecture ) , it might be good to have some specific guides on how to deal with this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Pete McNab edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I' m ran ve run into the same problem. I have a large ( 200kb 200+kb ) pipeline script that is generated from our legacy build specification language. My generated code is broken up into stages, with each stage running a potentially large parallel pipeline operation, where each platform of a given target is built. After some googling about the underlying cause, I attempted to break it up by having each stage be defined as a method and calling the method rather than just having all the code in one giant block, but it didn't help. As this will impact a lot of people trying to migrate to the Jenkins pipeline, and may make them throw up their hands due to the error being vague and unhelpful (which I realize is not the fault of Jenkins, but the underlying Java/Groovy architecture, it might be good to have some specific guides on how to deal with this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Pete McNab commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I'm ran into the same problem. I have a large (200kb) pipeline script that is generated from our legacy build specification language. My generated code is broken up into stages, with each stage running a potentially large parallel pipeline operation, where each platform of a given target is built. I attempted to break it up by having each stage be defined as a method and calling the method rather than just having all the code in one giant block, but it didn't help. As this will impact a lot of people trying to migrate to the Jenkins pipeline, and may make them throw up their hands due to the error being vague and unhelpful (which I realize is not the fault of Jenkins, but the underlying Java/Groovy architecture, it might be good to have some specific guides on how to deal with this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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. For more options, visit https://groups.google.com/d/optout.
