[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 kgiloo 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 you can only move your code at the script level in classes but you can't do this at the stage(s) level, which restricts drastically any refactoring. i have a parallel job running on 6 different platforms, "same" stages, but i have to copy-paste stages in a monster pipeline, which ends up into a 1130 lines call method. this is really a deal breaker in pure declarative. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-53152) MultiBranch Pipeline repository scan broken
Title: Message Title kgiloo created an issue Jenkins / JENKINS-53152 MultiBranch Pipeline repository scan broken Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2018-08-21 05:31 Environment: jenkins 2.133 Debian GNU/Linux 9 (stretch) credentials plugin 2.1.18 Pipeline Multibranch plugin 2.20 Priority: Critical Reporter: kgiloo Setup: multibranch pipeline based on subversion 1.8 after upgrading to credentials-plugin 2.1.18, my project is not scanned anymore, eventually displayed "NOT_BUILT". related log: Aug 20, 2018 7:45:00 AM jenkins.branch.MultiBranchProject$BranchIndexing run INFO: MY_MULTIBRANCH #20180820.074500 branch indexing action completed: NOT_BUILT in 47 ms Aug 20, 2018 7:45:00 AM hudson.model.Executor finish1 SEVERE: Executor threw an exception java.lang.LinkageError: com/cloudbees/plugins/credentials/domains/URIRequirementBuilder at jenkins.scm.impl.subversion.SubversionSCMSource.openSession(SubversionSCMSource.java:337) at jenkins.scm.impl.subversion.SubversionSCMSource.retrieve(SubversionSCMSource.java:240) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:357) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:267) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633)
[JIRA] (JENKINS-48776) Not able to trigger builds
Title: Message Title kgiloo commented on JENKINS-48776 Re: Not able to trigger builds Mike Foley : tested with Pipeline multibranch 2.19 and branch api plugin 2.0.20. it seems to work OKAY, but i had to reconfigure my job as "Multibranch pipeline" instead of "Bitbucket Team/project". The latter won't be scanned by jenkins at all. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48776) Not able to trigger builds
Title: Message Title kgiloo commented on JENKINS-48776 Re: Not able to trigger builds Mike Foley how did you deal with this issue? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48776) Not able to trigger builds
Title: Message Title kgiloo commented on JENKINS-48776 Re: Not able to trigger builds any update on this one? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48991) Artifactory plugin affected by JEP in 2.102
Title: Message Title kgiloo commented on JENKINS-48991 Re: Artifactory plugin affected by JEP in 2.102 Ajit Surana startup on master Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-48991) Artifactory plugin affected by JEP in 2.102
Title: Message Title kgiloo commented on JENKINS-48991 Re: Artifactory plugin affected by JEP in 2.102 for me, the options below do the workaround (as suggested in https://github.com/jenkinsci/artifactory-plugin/pull/30) JENKINS_JAVA_OPTIONS="-Dhudson.remoting.ClassFilter=org.jfrog.build.api.Artifact,org.jfrog.build.api.BaseBuildFileBean,org.jfrog.build.api.BaseBuildBean" Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] [nodeofflinenotification] (JENKINS-31075) SEVERE: Failed Loading plugin nodeofflinenotification
Title: Message Title kgiloo commented on JENKINS-31075 Re: SEVERE: Failed Loading plugin nodeofflinenotification after nightly safe restart, jenkins gets locked on "Please wait while jenkins is restarting...". no way to recover. reverted jenkins to old version... 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] [nodeofflinenotification] (JENKINS-31075) SEVERE: Failed Loading plugin nodeofflinenotification
Title: Message Title
kgiloo created an issue
Jenkins / JENKINS-31075
SEVERE: Failed Loading plugin nodeofflinenotification
Issue Type:
Bug
Assignee:
Unassigned
Components:
nodeofflinenotification
Created:
21/Oct/15 6:13 AM
Environment:
jenkins 1.634, mail watcher plugin 1.5
Priority:
Major
Reporter:
kgiloo
Since i upgraded from 1.617 to 1.634 i got EMs in the log, complaining about a faulty dependency between nodeofflinenotification (aka mail watcher plugin) and ruby-runtime: {{SEVERE: Failed Loading plugin ruby-runtime:
{{SEVERE: Failed Loading plugin ruby-runtime java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:441) at hudson.PluginManager$2$1$1.run(PluginManager.java:384) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$8.runTask(Jenkins.java:915) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassCircularityError: org/jruby/RubyClass at java.l
[JIRA] [core] (JENKINS-30563) It should be possible to display the Description of a project for "Parametrized builds"
Title: Message Title kgiloo created an issue Jenkins / JENKINS-30563 It should be possible to display the Description of a project for "Parametrized builds" Issue Type: Improvement Assignee: Unassigned Attachments: descr.png, descr0.png Components: core Created: 21/Sep/15 10:02 AM Environment: jenkins 1.625 Priority: Minor Reporter: kgiloo It could be very useful, when configuring a "Parametrized build" to enable Description to be displayed also. Initiator of the build would have an exact description of the job before trigering it.
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title Gilles Kacki commented on JENKINS-29876 Re: NPE when triggering downstream job (again) very silly bug. i was able to workaround it for some of my projects, removing "disabled" jobs from the downstreams. but for some other tasks without 'disabled' downstream jobs, it happens also. i do not get it. 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] [core] (JENKINS-23384) Stopping a jenkins clients marks many *other* clients as 'offline' in jenkins master
Gilles Kacki commented on JENKINS-23384 Stopping a jenkins clients marks many *other* clients as 'offline' in jenkins master Well i upgraded from jenkins 1.564 to 1.568 (slave 2.41 to 2.43) and i had exactly the same problem. One slave shutdown mess all the other ones. Disconnected slaves were not recognized anymore unless you kill jawaw.exe. Hence i wonder if you say this was supposed to be fixed in 1.568... Downgrade to 1.564 put things right. Any hint? 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.
