[JIRA] [job-dsl-plugin] (JENKINS-30832) Seed job encounters `NoClassDefFoundError`
Title: Message Title Ray H commented on JENKINS-30832 Re: Seed job encounters `NoClassDefFoundError` We already build a jar file and add it to the classpath via `additionalClasspath`. What I'm describing here is a regression we noticed. This worked for us in v1.38. There's only one import at the top (which is to import MonkeyPatcher). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-30832) Seed job encounters `NoClassDefFoundError`
Title: Message Title
Ray H commented on JENKINS-30832
Re: Seed job encounters `NoClassDefFoundError`
Unfortunately we do We haven't figured out how to get the same succinctness without MonkeyPatching. This is roughly our classes involved, I've omitted imports for brevity:
``` final class MonkeyPatcher { static { ToxWorkflow.init() }
// each DSL script calls this to ensure the monkey patching only happens once static void init() { } } ```
``` class ToxWorkflow { static function init() { Job.metaClass.fltox = { Closure null => steps { // <— complains that this closure could not be found virtualenv() //.. }
publishers {
} } } } ```
DSL Script: ``` MonkeyPatcher.init()
freeStyleJob('test') { fltox() }
```
I've added some prints inside MonkeyPatcher's static block, and I noticed that when the seed job runs successfully, the prints run for each job script that gets executed. When it fails, the prints don't show up (i.e. static block not being called)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [job-dsl-plugin] (JENKINS-30832) Seed job encounters `NoClassDefFoundError`
Title: Message Title
Ray H edited a comment on JENKINS-30832
Re: Seed job encounters `NoClassDefFoundError`
Unfortunately we do :( We haven't figured out how to get the same succinctness without MonkeyPatching. This is roughly our classes involved, I've omitted imports for brevity: ``` {code:groovy} final class MonkeyPatcher {static {ToxWorkflow.init()}// each DSL script calls this to ensure the monkey patching only happens oncestatic void init() { }} ``` {code} ``` {code:groovy} class ToxWorkflow {static function init() { Job.metaClass.fltox = { Closure null => steps { // <— complains that this closure could not be found virtualenv() //..} publishers { //.. } }}} ``` {code} DSL Script: ``` {code:groovy} MonkeyPatcher.init()freeStyleJob('test') {fltox()} {code} ```I've added some prints inside MonkeyPatcher's static block, and I noticed that when the seed job runs successfully, the prints run for each job script that gets executed. When it fails, the prints don't show up (i.e. static block not being called)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [job-dsl-plugin] (JENKINS-30832) Seed job encounters `NoClassDefFoundError`
Title: Message Title
Ray H edited a comment on JENKINS-30832
Re: Seed job encounters `NoClassDefFoundError`
Unfortunately we do :( We haven't figured out how to get the same succinctness without MonkeyPatching. This is roughly our classes involved, I've omitted imports for brevity:{code: groovy java }final class MonkeyPatcher {static {ToxWorkflow.init()}// each DSL script calls this to ensure the monkey patching only happens oncestatic void init() { }}{code}{code: groovy java }class ToxWorkflow {static function init() { Job.metaClass.fltox = { Closure null => steps { // <— complains that this closure could not be found virtualenv() //..} publishers {//.. } }}}{code}DSL Script:{code: groovy java }MonkeyPatcher.init()freeStyleJob('test') {fltox()}{code}```I've added some prints inside MonkeyPatcher's static block, and I noticed that when the seed job runs successfully, the prints run for each job script that gets executed. When it fails, the prints don't show up (i.e. static block not being called)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [job-dsl-plugin] (JENKINS-30832) Seed job encounters `NoClassDefFoundError`
Title: Message Title Ray H created an issue Jenkins / JENKINS-30832 Seed job encounters `NoClassDefFoundError` Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 07/Oct/15 11:25 PM Environment: Job DSL 1.39 Jenkins 1.631 Priority: Major Reporter: Ray H We've been tracing some errors since upgrading to 1.39 where certain classes no longer appeared to exist. We have a jar file which we add via "additionalClasspath" on our seed job. On inspection of the jar, the closure files do exist. ``` 16:37:06 java.lang.NoClassDefFoundError: com/freelancer/jobdsl/dsl/helpers/FreelancerToxWorkflowContext$_init_closure2_closure3 16:37:06 at com.freelancer.jobdsl.dsl.helpers.FreelancerToxWorkflowContext$_init_closure2.doCall(FreelancerToxWorkflowContext.groovy:60) ``` The weird thing is that we will make some changes to the source code, but the errors still point to the same location (line 60) where it can't find the class. We suspect there'ssome nasty caching going on. Furthermore, we tried to track down which commit this started happening, and found it started happening when trying to clean up the
[JIRA] [job-dsl-plugin] (JENKINS-30832) Seed job encounters `NoClassDefFoundError`
Title: Message Title Ray H updated an issue Jenkins / JENKINS-30832 Seed job encounters `NoClassDefFoundError` Change By: Ray H We've been tracing some errors since upgrading to 1.39 where certain classes no longer appeared to exist. We have a jar file which we add via "additionalClasspath" on our seed job.On inspection of the jar, the closure files do exist.```16:37:06 java.lang.NoClassDefFoundError: com/freelancer/jobdsl/dsl/helpers/FreelancerToxWorkflowContext$_init_closure2_closure316:37:06 at com.freelancer.jobdsl.dsl.helpers.FreelancerToxWorkflowContext$_init_closure2.doCall(FreelancerToxWorkflowContext.groovy:60)```The weird thing is that we will tried make some changes to the source code, but the errors still point to the same location ( says line 60) where it can't find the class. We suspect there'ssome nasty caching going on. Furthermore, we tried to track down which commit this started happening, and found it started happening when trying to clean up the classloader: https://github.com/jenkinsci/job-dsl-plugin/commit/98ad52ac530dc58156807cd7dca29f323301042c ?w=1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Ray H commented on JENKINS-30504 Re: Occasional StackOverflow using `downstreamParameterized` publisher Cheers. I should have specifically mentioned use of `gradle` to do this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Ray H commented on JENKINS-30504 Re: Occasional StackOverflow using `downstreamParameterized` publisher That sounds reasonable. We also compile our own library using `job-dsl-plugin` and we match `job-dsl-plugin`'s dependency versions to avoid running into untested behavior. The bug is difficult to diagnose no a Jenkins instance, because when the StackOverflowError happens, the job enters a zombie state (and you can't cancel it JENKINS-30271) and the logs do not be shipped back to the Jenkins master so no one knows if/why "StackOverflowError" happens. I've tested this fix on a snapshot build on a Ubuntu Jenkins Master/Slave running Java 1.8 and the problem no longer Is this patch a reasonable solution considering that Jenkins supports use of Java8? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Ray H commented on JENKINS-30504 Re: Occasional StackOverflow using `downstreamParameterized` publisher I tried running this against Java 7 and I did not see the StackOverflow error. Perhaps it's something that has changed from Java 7 to Java 8. What was the environment you were testing under? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Ray H updated an issue Jenkins / JENKINS-30504 Occasional StackOverflow using `downstreamParameterized` publisher Change By: Ray H Environment: java version "1.8.0_60"Java(TM) SE Runtime Environment (build 1.8.0_60-b27)Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) Saw error in both: job-dsl-plugin:1.38, job-dsl-plugin:1.39-SNAPSHOT Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Ray H updated an issue Jenkins / JENKINS-30504 Occasional StackOverflow using `downstreamParameterized` publisher Change By: Ray H Environment: java version "1.8.0_60"Java(TM) SE Runtime Environment (build 1.8.0_60-b27)Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)Saw error in both: job-dsl-plugin : 1.38 , job-dsl-plugin: & 1.39-SNAPSHOT Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Ray H commented on JENKINS-30504 Re: Occasional StackOverflow using `downstreamParameterized` publisher I've attached a pull request which seems to fix this for me. See: https://github.com/jenkinsci/job-dsl-plugin/pull/615 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [job-dsl-plugin] (JENKINS-30504) Occasional StackOverflow using `downstreamParameterized` publisher
Title: Message Title Ray H created an issue Jenkins / JENKINS-30504 Occasional StackOverflow using `downstreamParameterized` publisher Issue Type: Bug Assignee: Daniel Spilker Attachments: jobdsl-stackoverflow.txt Components: job-dsl-plugin Created: 17/Sep/15 12:30 AM Environment: java version "1.8.0_60" Java(TM) SE Runtime Environment (build 1.8.0_60-b27) Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) Labels: job-dsl Priority: Critical Reporter: Ray H On our environment, we're occasionally seeing StackOverflows which seems to be traced to `downstreamParameterized`. When run on my local machine, I see the StackOverflow but am able to generate XML files. However, on a Jenkins instance, we're occasionally seeing
[JIRA] [gitlab-hook-plugin] (JENKINS-28808) 'undefined method `extensions'' on processing Multiple SCMs projects
Title: Message Title Ray H commented on JENKINS-28808 Re: 'undefined method `extensions'' on processing Multiple SCMs projects I am seeing this issue as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [s3-plugin] (JENKINS-26681) Improve Performance of S3 Entry upload which contain a *lot* of files
Ray H created JENKINS-26681 Improve Performance of S3 Entry upload which contain a *lot* of files Issue Type: Bug Assignee: Unassigned Components: s3-plugin Created: 29/Jan/15 8:34 AM Description: This can be a little frustrating when you're trying to upload alot of files to S3, i.e. updating a static site. This is more of an implementation issue where the current approach (while clever), tries to flatten all the upload requests and uploads them one at a time. The better approach would be to use a TransferManager and batch upload all the Entries together. I want to take this on but there's some code I'd like to refactor to get there. Project: Jenkins Priority: Minor Reporter: Ray H This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [s3-plugin] (JENKINS-23432) S3 publisher fails with String index out of range error
Ray H commented on JENKINS-23432 S3 publisher fails with String index out of range error So it sounds like the problem is related to people's expectation is that the S3 plugin should take a comma separated list b/c the ANT path specifier usually allows that. I think it'd be reasonable to actually support comma separated values. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [s3-plugin] (JENKINS-23432) S3 publisher fails with String index out of range error
Ray H edited a comment on JENKINS-23432 S3 publisher fails with String index out of range error So it sounds like the problem is related to people's expectation is that the S3 plugin should take a comma separated list b/c the ANT path specifier usually allows that. I think it'd be reasonable to actually support comma separated values. However is this reimplementing the idea of having multiple entries. Hm? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [s3-plugin] (JENKINS-16025) Allow full path when uploading a file
Ray H commented on JENKINS-16025 Allow full path when uploading a file IMO it seems that if we want to make this less 'magical', we should allow the user to specify a prefix path, i.e. if I have a file at foo/bar/baz/qux.zip. Then I'd specify: prefixPath = foo/bar search=baz/* so that when I upload to `myBucket`, it should uploaded to s3://myBucket/baz/qux.zip` whereas the current behavior: of specifying sourceFile = `foo/bar/baz/*` would upload it to the root directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [job-dsl-plugin] (JENKINS-26561) Releases after 0.7 breaks compatibility to job-dsl
Ray H created JENKINS-26561 Releases after 0.7 breaks compatibility to job-dsl Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin, s3-plugin Created: 22/Jan/15 8:22 PM Description: The enum lookup for selecting the region has changed between 0.6 0.7. I think the approach here should be graceful to support both enum lookups for the time being. I've submitted a pull request: https://github.com/jenkinsci/s3-plugin/pull/46 Project: Jenkins Priority: Major Reporter: Ray H This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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.
