[JIRA] (JENKINS-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Ronen Peleg updated an issue Jenkins / JENKINS-40695 Allow running Pipeline shared library functions on executor Change By: Ronen Peleg Comment: For me, Libraries = GIT Repository which means temporary files to the Master! without cleanup control system. To download repository (call it library if you want but it's a fully source repository files) to the master without properly cleanup system it's a recipe for disaster! Also the Master need to stay clean all the time without a jobs/builds temporary files as library... I also like the suggestion of add new option to run all the pipeline project in specific node, as we already have and exist in normal Jenkins job: "Restrict where this project can be run". so simple so smart.There must be a way to allow users to control the node to where download the library...I don't see any reason that you prevent us from getting this new option. 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
[JIRA] (JENKINS-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Ronen Peleg commented on JENKINS-40695 Re: Allow running Pipeline shared library functions on executor For me, Libraries = GIT Repository which means temporary files to the Master! without cleanup control system. To download repository (call it library if you want but it's a fully source repository files) to the master without properly cleanup system it's a recipe for disaster! Also the Master need to stay clean all the time without a jobs/builds temporary files as library... I also like the suggestion of add new option to run all the pipeline project in specific node, as we already have and exist in normal Jenkins job: "Restrict where this project can be run". so simple so smart. There must be a way to allow users to control the node to where download the library... I don't see any reason that you prevent us from getting this new option. 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-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Ronen Peleg edited a comment on JENKINS-40695 Re: Allow running Pipeline shared library functions on executor For me, Libraries = GIT Repository which means temporary files to the Master! without cleanup control system. To download repository (call it library if you want but it's a fully source repository files) to the master without properly cleanup system it's a recipe for disaster! Also the Master need to stay clean all the time without a jobs/builds temporary files as library... I also like the suggestion of add new option to run all the pipeline project in specific node, as we already have and exist in normal Jenkins job: "Restrict where this project can be run". so simple so smart.There must be a way to allow users to control the node to where download the library... I don't see any reason that you prevent us from getting this new option. 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-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Ronen Peleg reopened an issue For me, Libraries = GIT Repository which means temporary files to the Master! without cleanup control system. I don't see any reason that you prevent us from getting this new option. BTW: This feature is already exist on Jenkins normal job (see Jenkins job option: "Restrict where this project can be run"). Reopen this ticket... 10x Jenkins / JENKINS-40695 Allow running Pipeline shared library functions on executor Change By: Ronen Peleg Resolution: Won't Do Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Ronen Peleg updated an issue Jenkins / JENKINS-40695 Allow running Pipeline shared library functions on executor Change By: Ronen Peleg Comment: For me, Libraries = GIT Repository which means temporary files to the Master! without cleanup control system.I don't see any reason that you prevent us from getting this new option. BTW: This feature is already exist on Jenkins normal job (see Jenkins job option: "Restrict where this project can be run").Reopen this ticket... 10x 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-40695) Allow running Pipeline shared library functions on executor
Title: Message Title Ronen Peleg commented on JENKINS-40695 Re: Allow running Pipeline shared library functions on executor To download repository (call it library if you want but it's a fully source repository files) to the master without properly cleanup system it's a recipe for disaster! Also the Master need to stay clean all the time without a jobs/builds temporary files as library... I also like the suggestion of add new option to run all the pipeline project in specific node, as we already have and exist in normal Jenkins job: "Restrict where this project can be run". so simple so smart. There must be a way to allow users to control the node to where download the library... 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] [active-directory-plugin] (JENKINS-8119) Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.1
Title: Message Title Ronen Peleg commented on JENKINS-8119 Re: Active Directory Plugin version 1.17 results in org.acegisecurity.BadCredentialsException: Either no such user 'kgraham' or incorrect password, when 1.16 does not Same problem here, using plugin version 1.45, it's only a warning but my logs is full with these warning, why? 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] [ssh-slaves-plugin] (JENKINS-23419) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
Title: Message Title
Ronen Peleg edited a comment on JENKINS-23419
Re: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
{color:red}Same issue starting to happen on my system - Jenkins ver. LTS 1.580.3, any solution?{color}BTW: If I rebuild the same failed build again after few minutes, the build is passe successfully. {color:#707070} _04 04 :15:12 Wiping out workspace first.04:15:13 FATAL: java.io.IOException: Unexpected EOF04:15:13 hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF04:15:13 at hudson.remoting.Request.abort(Request.java:295)04:15:13 at hudson.remoting.Channel.terminate(Channel.java:814)04:15:13 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)04:15:13 at ..remote call to mydtbld0147.hpeswlab.net(Native Method)04:15:13 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)04:15:13 at hudson.remoting.Request.call(Request.java:171)04:15:13 at hudson.remoting.Channel.call(Channel.java:751)04:15:13 at hudson.FilePath.act(FilePath.java:969)04:15:13 at hudson.FilePath.act(FilePath.java:958)04:15:13 at hudson.FilePath.deleteContents(FilePath.java:1173)04:15:13 at hudson.plugins.git.extensions.impl.WipeWorkspace.beforeCheckout(WipeWorkspace.java:28)04:15:13 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:981)04:15:13 at hudson.scm.SCM.checkout(SCM.java:488)04:15:13 at hudson.model.AbstractProject.checkout(AbstractProject.java:1257)04:15:13 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)04:15:13 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)04:15:13 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)04:15:13 at hudson.model.Run.execute(Run.java:1745)04:15:13 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)04:15:13 at hudson.model.ResourceController.execute(ResourceController.java:89)04:15:13 at hudson.model.Executor.run(Executor.java:240)04:15:13 Caused by: java.io.IOException: Unexpected EOF04:15:13 at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:99)04:15:13 at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33)04:15:13 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)04:15:13 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) _ {color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ssh-slaves-plugin] (JENKINS-23419) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
Title: Message Title
Ronen Peleg edited a comment on JENKINS-23419
Re: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
{color:red}Same issue starting to happen on my system - Jenkins ver. LTS 1.580.3, any solution?{color}BTW: If I rebuild the same failed build again after few minutes, the build is passe successfully.{color:# cc 707070 } 04 _04 :15:12 Wiping out workspace first.04:15:13 FATAL: java.io.IOException: Unexpected EOF04:15:13 hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF04:15:13 at hudson.remoting.Request.abort(Request.java:295)04:15:13 at hudson.remoting.Channel.terminate(Channel.java:814)04:15:13 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)04:15:13 at ..remote call to mydtbld0147.hpeswlab.net(Native Method)04:15:13 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356)04:15:13 at hudson.remoting.Request.call(Request.java:171)04:15:13 at hudson.remoting.Channel.call(Channel.java:751)04:15:13 at hudson.FilePath.act(FilePath.java:969)04:15:13 at hudson.FilePath.act(FilePath.java:958)04:15:13 at hudson.FilePath.deleteContents(FilePath.java:1173)04:15:13 at hudson.plugins.git.extensions.impl.WipeWorkspace.beforeCheckout(WipeWorkspace.java:28)04:15:13 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:981)04:15:13 at hudson.scm.SCM.checkout(SCM.java:488)04:15:13 at hudson.model.AbstractProject.checkout(AbstractProject.java:1257)04:15:13 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622)04:15:13 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)04:15:13 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528)04:15:13 at hudson.model.Run.execute(Run.java:1745)04:15:13 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)04:15:13 at hudson.model.ResourceController.execute(ResourceController.java:89)04:15:13 at hudson.model.Executor.run(Executor.java:240)04:15:13 Caused by: java.io.IOException: Unexpected EOF04:15:13 at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:99)04:15:13 at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33)04:15:13 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)04:15:13 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) _ {color}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ssh-slaves-plugin] (JENKINS-23419) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
Title: Message Title Ronen Peleg updated an issue Jenkins / JENKINS-23419 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF Change By: Ronen Peleg Labels: 1.565 1.580.3 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] [ssh-slaves-plugin] (JENKINS-23419) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF
Title: Message Title Ronen Peleg commented on JENKINS-23419 Re: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF Same issue starting to happen on my system - Jenkins ver. LTS 1.580.3, any solution? BTW: If I rebuild the same failed build again after few minutes, the build is passe successfully. 04:15:12 Wiping out workspace first. 04:15:13 FATAL: java.io.IOException: Unexpected EOF 04:15:13 hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected EOF 04:15:13 at hudson.remoting.Request.abort(Request.java:295) 04:15:13 at hudson.remoting.Channel.terminate(Channel.java:814) 04:15:13 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) 04:15:13 at ..remote call to mydtbld0147.hpeswlab.net(Native Method) 04:15:13 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) 04:15:13 at hudson.remoting.Request.call(Request.java:171) 04:15:13 at hudson.remoting.Channel.call(Channel.java:751) 04:15:13 at hudson.FilePath.act(FilePath.java:969) 04:15:13 at hudson.FilePath.act(FilePath.java:958) 04:15:13 at hudson.FilePath.deleteContents(FilePath.java:1173) 04:15:13 at hudson.plugins.git.extensions.impl.WipeWorkspace.beforeCheckout(WipeWorkspace.java:28) 04:15:13 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:981) 04:15:13 at hudson.scm.SCM.checkout(SCM.java:488) 04:15:13 at hudson.model.AbstractProject.checkout(AbstractProject.java:1257) 04:15:13 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) 04:15:13 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 04:15:13 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) 04:15:13 at hudson.model.Run.execute(Run.java:1745) 04:15:13 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 04:15:13 at hudson.model.ResourceController.execute(ResourceController.java:89) 04:15:13 at hudson.model.Executor.run(Executor.java:240) 04:15:13 Caused by: java.io.IOException: Unexpected EOF 04:15:13 at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:99) 04:15:13 at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:33) 04:15:13 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) 04:15:13 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Add Comment This message was sent by Atlassian JIRA
[JIRA] [findbugs-plugin] (JENKINS-8174) no details in findbugs view
Ronen Peleg commented on JENKINS-8174 no details in findbugs view You need to provide a fix since you are the developer, I just wakeup this issue because it's the same issue (and why to open a new one?!). On my Jenkins LTS it's now working fine and I test it on two difference Jenkins LTS machine. Try it on Jenkins LTS version: 1.580.3 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] [findbugs-plugin] (JENKINS-8174) no details in findbugs view
Ronen Peleg commented on JENKINS-8174 no details in findbugs view It's fact that on FindBugs Plugin Version 4.57 the plugin works just fine on my Jenkins LTS 1.580.3, and with your latest FindBugs Plugin version 4.59 and not working (no details in findbugs view). 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] [findbugs-plugin] (JENKINS-8174) no details in findbugs view
Ronen Peleg edited a comment on JENKINS-8174 no details in findbugs view You need to provide a fix since you are the developer, I just wakeup this issue because it's the same issue (and why to open a new one?!). On my Jenkins LTS it's NOT working and I test it on two difference Jenkins LTS machine. Try it on Jenkins LTS version: 1.580.3 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] [findbugs-plugin] (JENKINS-8174) no details in findbugs view
Ronen Peleg reopened JENKINS-8174 no details in findbugs view Change By: Ronen Peleg (12/Mar/15 5:20 PM) Resolution: WontFix Status: Closed Reopened Assignee: UlliHafner RonenPeleg 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] [findbugs-plugin] (JENKINS-8174) no details in findbugs view
Ronen Peleg commented on JENKINS-8174 no details in findbugs view Same Issue on Jenkins LTS 1.580.3 with FindBugs Plugin v4.59 and Static Analysis Utilities v1.70 I'm running Jenkins under Jetty on Linux Red Hat. Any Idea? 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] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg edited a comment on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 @Oleg Nenashev, Did you try it with 1200 active jobs? anyway this is what solved my problem. I guess you have issue with 100+ slave machines connected to Jenkins with high load Jenkins. @Kohsuke Kawaguchi, because I have 64GB RAM, I can't do it, I can't save 64GB RAM on my HDD and anyway my problem is already solved so it's save to close it. 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] [findbugs-plugin] (JENKINS-8174) no details in findbugs view
Ronen Peleg commented on JENKINS-8174 no details in findbugs view UPDATE: I downgrade the plugin to version: 4.57 and the problem is solved and @Ulli Hafner as you understand you definitely have a BUG on your plugin on Jenkins version LTS 1.580.3, so please fix it. 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] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg closed JENKINS-20620 as Incomplete Memory Leak on Jenkins LTS 1.509.4/1.532.1 Change By: Ronen Peleg (12/Mar/15 6:41 PM) Status: Resolved Closed 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] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 @Oleg Nenashev, this is what solved my problem. I guess you have issue with 100+ slave machines connected to Jenkins. @Kohsuke Kawaguchi, because I have 64GB RAM, I can't do it, I can't save 64GB RAM on my HDD and anyway my problem is already solved so it's save to close it. 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] [core] (JENKINS-3963) JDK auto install from j.s.c need to be able to specify 32bit/64bit
Ronen Peleg edited a comment on JENKINS-3963 JDK auto install from j.s.c need to be able to specify 32bit/64bit We still don't have this option, why? 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/groups/opt_out.
[JIRA] [core] (JENKINS-3963) JDK auto install from j.s.c need to be able to specify 32bit/64bit
Ronen Peleg commented on JENKINS-3963 JDK auto install from j.s.c need to be able to specify 32bit/64bit Still we don't have this option, why? 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Update: The solution was to delete some slave machines from the Jenkins nodes. It turns out that Jenkins can't handle more than 100 slave machines. Currently we have (after cleanup) 70 slave machines and no memory leak! BTW: The memory leak issue occurs only on Jenkins Master running on Linux O/S with more than 100 slave machines, Actually on Windows O/S this issue doesn't exist! 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Thanks Oleg. I can't dump it because it's to big (40GB) and for some reason the "jmap" unable to connect to the Jenkins process. Anyway I downgraded the version to 1.537... Oleg, If you have a system with 600 jobs with high activities + 40 slave machines online and you don't have this issue it's very strange because I test these versions on several different machines and each time the problem reproduced (after 12-24 hours). 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Oleg, I sent you email with our Jenkins Plugins list. Thank You 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Update: I checked the release version: 1.539 that on JoJ, this version is memory leaks free but this version suffers from other bugs such as problem when using Build multi-configuration project (Matrix job) + Builds of a concurrently executable job. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Update: I checked also the 1.54X versions (1.541, 1.542, 1.543, 1.544) and the memory leak issue is also on all release 1.54X versions! 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Thank You for your help First with all the respect to JoJ they doesn't have the system load that we are facing here and has you can see it's snapshots version. Anyway, I didn't try the release version 1.539... BTW: In order to solve memory leaks you must use load software such as Load Runner. I tried the new LTS versions after update plugins and without update plugins, still the same issue same bug and as I wrote this bug doesn't happens on previous version at all. Of course it community, open source and all of that... but don't forget there is also Enterprise edition that including "Jenkins support team" and I just wonder why they not solving this super critical issue but I guess this all another story... 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Change By: Ronen Peleg (16/Dec/13 9:14 AM) Environment: LinuxServerwith24CPUsand64GBRAMJenkinsversionLTS1.509.4/1.532.1onJettyMemoryallocatedforJenkins/Jettyprocess:42GB Load Environment :Jenkinsworkingwith600jobswithhighactivities +40slavemachines(LinuxandWindows) 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/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-20635) Add Run Command for Windows
Ronen Peleg closed JENKINS-20635 as Not A Defect Add Run Command for Windows Change By: Ronen Peleg (03/Dec/13 6:58 AM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-20635) Add Run Command for Windows
Ronen Peleg commented on JENKINS-20635 Add Run Command for Windows Thanks 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Change By: Ronen Peleg (04/Dec/13 6:36 AM) Labels: 1.509.4 1.509.4LTS1.532.11.532.1LTS JenkinsLTS Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...TEST#1onLTS1.509.4:1.MachinewithJettyupafterrestart2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB-Memoryleaksbetween10:00-10:20asyoucanseeafterGCitsstillthinkJavain-useandfailtocleanuptheallmemoryasitshouldbe.5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100%TEST#2onLTS1.509.4:ItriedtodomanualGC,Doesnthelp!(seeattachfile:Monitor_Memory_Over_Time_Manual_GC)TEST#3onLTS1.509.3:UnfortunatelyIdowngradetoLTS1.509.3because ofthe memoryleak , formeitsablockerissue! On BTW:In versionLTS1.509.3Jenkinsworksstablewithoutanymemoryleaks...(seeattachfile:Good_GC_A1.509.3) butwithonebigunsolvedproblem,Icantrenamejobs(deadlock)!TEST#4withLTS1 . 532.1: Sameissue!Jenkinsstuckwith100%memoryusageafteronly12hours! Thanks ThankYou ,Ronen. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Change By: Ronen Peleg (04/Dec/13 5:27 AM) Summary: MemoryLeakonJenkinsLTS1.509.4 /1.532.1 Environment: LinuxServerwith24CPUsand64GBRAMJenkinsversionLTS1.509.4 /1.532.1 onJettyMemoryallocatedforJenkins/Jettyprocess:42GBLoad:Jenkinsworkingwith600jobswithhighactivities 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4
Ronen Peleg commented on JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4 The same problem happens with 1.532.1 LTS ! 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4/1.532.1
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4/1.532.1 Change By: Ronen Peleg (04/Dec/13 8:27 PM) Attachment: Good_GC_B1.509.3.jpg Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...TEST#1onLTS1.509.4:1.MachinewithJettyupafterrestart2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB-Memoryleaksbetween10:00-10:20asyoucanseeafterGCitsstillthinkJavain-useandfailtocleanuptheallmemoryasitshouldbe.5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100%TEST#2onLTS1.509.4:ItriedtodomanualGC,Doesnthelp!(seeattachfile:Monitor_Memory_Over_Time_Manual_GC)TEST#3onLTS1.509.3:UnfortunatelyIdowngradetoLTS1.509.3becauseofthememoryleak,formeitsablockerissue! BTW:In Pleasenotethaton versionLTS1.509.3Jenkinsworksstable evenonhighenvironment withoutanymemory leaks leak ...( see See attach file files :Good_GC_A1.509.3 andGood_GC_B1.509.3 )but withonebig unfortunatelythereisaBIG unsolvedproblem /buginthisversion ,Icantrenamejobs( deadlock) Deadlock ! whichsolvedonthenextversionLTS1.509.4/1.532.1thatIcantusebecauseofthememoryleak). TEST#4withLTS1.532.1:Sameissue!Jenkinsstuckwith100%memoryusageafteronly12hours!ThankYou,Ronen. 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/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-20635) Add Run Command for Windows
Ronen Peleg created JENKINS-20635 Add Run Command for Windows Issue Type: Task Assignee: Oleg Nenashev Components: customtools-plugin Created: 18/Nov/13 8:27 PM Description: Hi, As I understand and checked, The current "Run Command" option work only on Linux (ssh/shell) OS. It will be great if you can add "Run Command" for Windows (cmd) OS. Thanks, Ronen. Environment: Jenkins Master on Linux machine with Windows 2008 slave machine Project: Jenkins Priority: Major Reporter: Ronen Peleg 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leaks on Jenkins LTS 1.509.4
Ronen Peleg created JENKINS-20620 Memory Leaks on Jenkins LTS 1.509.4 Issue Type: Bug Assignee: Ronen Peleg Attachments: Monitor_After_12_Hours.jpg, Monitor_After_1_Hour.jpg, Monitor_After_20_Hours.jpg, Monitor_After_23_Hours.JPG Components: core Created: 17/Nov/13 10:18 AM Description: After Jenkins upgraded to LTS 1.509.4 from LTS 1.509.3 I notice that over time (24 hours) Jenkins becomes very slowly. It turns out that Jenkins (under Jetty service) slowly "eats" the server memory. It's takes about 24 hours to take all the memory allocated to Jenkins (42GB). See the snapshots with examples... 1. Machine with Jetty up after restart. 2. Jenkins Used - After one Hour: 22GB 3. Jenkins Used - After 12 Hours: 27GB 4. Jenkins Used - After 20 Hours: 35GB 5. Jenkins Used - After 24 Hours: 39GB (Very slow) Thanks, Ronen. Environment: Linux Server with 24 CPUs and 64GB RAM Jenkins version LTS 1.509.4 on Jetty Memory allocated for Jenkins/Jetty process: 42GB Jenkins working with 600 jobs Project: Jenkins Priority: Critical Reporter: Ronen Peleg 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leaks on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leaks on Jenkins LTS 1.509.4 Change By: Ronen Peleg (17/Nov/13 10:27 AM) Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...1.MachinewithJettyupafterrestart.2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB5.JenkinsUsed-After 24 23 Hours:39GB ( - Veryslow ) responseandHeapisalmost100%! Thanks,Ronen. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leaks on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leaks on Jenkins LTS 1.509.4 Change By: Ronen Peleg (17/Nov/13 10:20 AM) Labels: 1.509.4JenkinsLTS 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leaks on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leaks on Jenkins LTS 1.509.4 Change By: Ronen Peleg (17/Nov/13 2:44 PM) Attachment: Monitor_Memory_Over_Time_Manual_GC.jpg Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...1.MachinewithJettyupafterrestart . 2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB -Memoryleaksbetween10:00-10:20(asyoucanseeafterGCitsstillthinkmemoryin-use) 5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100%! 6.Seealsoanothertestonattachfile:Monitor_Memory_Over_Time_Manual_GCwhenItriedtodomanualGC.Alsodoesnthelp. Thanks,Ronen. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leaks on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leaks on Jenkins LTS 1.509.4 Change By: Ronen Peleg (17/Nov/13 2:53 PM) Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...1.MachinewithJettyupafterrestart2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB-Memoryleaksbetween10:00-10:20 ( asyoucanseeafterGCitsstillthink memory Java in-use ) andfailtocleanuptheallmemoryasitshouldbe. 5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100% ! 6.Seealsoanothertest(Attachfile:Monitor_Memory_Over_Time_Manual_GC)ItriedtodomanualGC,Doesnthelp! BTW:OnversionLTS1.509.3Jenkinsworkstablewithoutanymemoryleaks... Thanks,Ronen. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leaks on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leaks on Jenkins LTS 1.509.4 Change By: Ronen Peleg (17/Nov/13 2:46 PM) Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...1.MachinewithJettyupafterrestart2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB-Memoryleaksbetween10:00-10:20(asyoucanseeafterGCitsstillthinkmemoryin-use)5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100%!6.Seealsoanothertest onattach (Attach file: Monitor_Memory_Over_Time_Manual_GC when ) ItriedtodomanualGC .Alsodoesn ,Doesn thelp . ! Thanks,Ronen. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leaks on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leaks on Jenkins LTS 1.509.4 Change By: Ronen Peleg (17/Nov/13 2:47 PM) Environment: LinuxServerwith24CPUsand64GBRAMJenkinsversionLTS1.509.4onJettyMemoryallocatedforJenkins/Jettyprocess:42GB Load: Jenkinsworkingwith600jobs withhighactivities 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leaks on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leaks on Jenkins LTS 1.509.4 Change By: Ronen Peleg (17/Nov/13 2:54 PM) Attachment: gc.log 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4 Change By: Ronen Peleg (18/Nov/13 5:49 AM) Summary: Memory Leaks Leak onJenkinsLTS1.509.4 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4 Change By: Ronen Peleg (18/Nov/13 5:51 AM) Assignee: RonenPeleg 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4 Change By: Ronen Peleg (18/Nov/13 7:51 AM) Attachment: Good_GC_A1.509.3.JPG Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples... TEST# 1 :1 .MachinewithJettyupafterrestart2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB-Memoryleaksbetween10:00-10:20asyoucanseeafterGCitsstillthinkJavain-useandfailtocleanuptheallmemoryasitshouldbe.5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100% 6. TEST#2: See alsoanothertest( Attachfile:Monitor_Memory_Over_Time_Manual_GC ) - ItriedtodomanualGC,Doesnthelp! BTW DOWNGRADE : UnfortunatelyIdowngradetoLTS1.509.3becausememoryleakformeitsablockerissue! OnversionLTS1.509.3Jenkinsworkstablewithoutanymemoryleaks... (seeattachfile:Good_GC_A1.509.3). Thanks,Ronen. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4 Change By: Ronen Peleg (18/Nov/13 7:53 AM) Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...TEST#1onLTS1.509.4: 1.MachinewithJettyupafterrestart2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB-Memoryleaksbetween10:00-10:20asyoucanseeafterGCitsstillthinkJavain-useandfailtocleanuptheallmemoryasitshouldbe.5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100% TEST#2onLTS1.509.4: SeeAttachfile:Monitor_Memory_Over_Time_Manual_GC- ItriedtodomanualGC,Doesnthelp! (seeattachfile:Monitor_Memory_Over_Time_Manual_GC) TEST#3onLTS1.509.3: UnfortunatelyIdowngradetoLTS1.509.3becausememoryleakformeitsablockerissue!OnversionLTS1.509.3Jenkinsworkstablewithoutanymemoryleaks...(seeattachfile:Good_GC_A1.509.3).Thanks,Ronen. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4 Change By: Ronen Peleg (18/Nov/13 7:53 AM) Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...TEST#1 onLTS1.509.4 : 1.MachinewithJettyupafterrestart2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB-Memoryleaksbetween10:00-10:20asyoucanseeafterGCitsstillthinkJavain-useandfailtocleanuptheallmemoryasitshouldbe.5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100% TEST#2 onLTS1.509.4 : SeeAttachfile:Monitor_Memory_Over_Time_Manual_GC-ItriedtodomanualGC,Doesnthelp! DOWNGRADE TEST#3onLTS1.509.3 : UnfortunatelyIdowngradetoLTS1.509.3becausememoryleakformeitsablockerissue!OnversionLTS1.509.3Jenkinsworkstablewithoutanymemoryleaks...(seeattachfile:Good_GC_A1.509.3).Thanks,Ronen. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20620) Memory Leak on Jenkins LTS 1.509.4
Ronen Peleg updated JENKINS-20620 Memory Leak on Jenkins LTS 1.509.4 Change By: Ronen Peleg (18/Nov/13 7:56 AM) Description: AfterJenkinsupgradedtoLTS1.509.4fromLTS1.509.3Inoticethatovertime(24hours)Jenkinsbecomesveryslowly.ItturnsoutthatJenkins(underJettyservice)slowlyeatstheservermemory.Itstakesabout24hourstotakeallthememoryallocatedtoJenkins(42GB).Seethesnapshotswithexamples...TEST#1onLTS1.509.4:1.MachinewithJettyupafterrestart2.JenkinsUsed-AfteroneHour:22GB3.JenkinsUsed-After12Hours:27GB4.JenkinsUsed-After20Hours:35GB-Memoryleaksbetween10:00-10:20asyoucanseeafterGCitsstillthinkJavain-useandfailtocleanuptheallmemoryasitshouldbe.5.JenkinsUsed-After23Hours:39GB-VeryslowresponseandHeapisalmost100%TEST#2onLTS1.509.4:ItriedtodomanualGC,Doesnthelp!(seeattachfile:Monitor_Memory_Over_Time_Manual_GC)TEST#3onLTS1.509.3:UnfortunatelyIdowngradetoLTS1.509.3becausememoryleakformeitsablockerissue!OnversionLTS1.509.3Jenkins work works stablewithoutanymemoryleaks...(seeattachfile:Good_GC_A1.509.3).Thanks,Ronen. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20512) Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins
Sega created JENKINS-20512 Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins Issue Type: Bug Assignee: Sega Attachments: gitpollingissue.JPG, gitpollingok.JPG Components: git Created: 11/Nov/13 11:32 AM Description: Hi, I am experiencing a problem on the GIT polling and here are the details: When the option "Branches to build" on GIT Plugin for Jenkins is "blank" or "**" the GIT polling working just fine but when I entered "master" or "origin/master" or other to option "Branches to build" the GIT polling crashes with the following error (see also snapshot): Started on Nov 11, 2013 1:15:13 PM Using strategy: Default poll Last Built Revision: Revision 1d530845b2467e9e342fbf19e101c1291e1458a9 (origin/master) FATAL: Error performing command: ls-remote -h ssh://g...@mymachine0005.us.mycompany.com:7999/LT/ltpc.git master hudson.util.IOException2: Error performing command: ls-remote -h ssh://g...@mymachine0005.us.mycompany.com:7999/LT/ltpc.git master at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:458) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1530) at hudson.model.AbstractProject.poll(AbstractProject.java:1455) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: hudson.plugins.git.GitException: Error performing command: ls-remote -h ssh://g...@mymachine0005.us.mycompany.com:7999/LT/ltpc.git master at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:988) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:920) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:1297) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:488) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:456) ... 13 more Caused by: java.io.IOException: Cannot run program "git.exe": CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:773) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:977) ... 17 more Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.init(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 23 more Done. Took 0.37 sec No changes Any Idea? Thank You for your support, Ronen. Due Date: 11/Nov/13 12:00 AM Environment: Jenkins version 1.509.4 on Windows 2008 R2 Jenkins GIT plugin v2.0 Jenkins GIT client plugin v1.4.6 GIT Client for Windows v1.8 Project: Jenkins Labels: polling scm git, Priority: Critical
[JIRA] [git] (JENKINS-20512) Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins
Ronen Peleg updated JENKINS-20512 Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins Change By: Ronen Peleg (11/Nov/13 11:40 AM) Summary: GitPlugin2.0: FailureonGitPollingLogwhenusingoptionBranchestobuildonGitPluginforJenkins Environment: Jenkinsversion1.509.4onWindows2008R2 SlaveisrunningonWindowsServer2008R2 JenkinsGITpluginv2.0JenkinsGITclientpluginv1.4.6GITClientforWindowsv1.8 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/groups/opt_out.
[JIRA] [git] (JENKINS-20512) Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins
Ronen Peleg updated JENKINS-20512 Git Plugin 2.0: Failure on Git Polling Log when using option Branches to build on Git Plugin for Jenkins Change By: Ronen Peleg (11/Nov/13 12:20 PM) Environment: Jenkinsversion1.509.4onWindows2008R2SlaveisrunningonWindowsServer2008R2JenkinsGITpluginv2.0JenkinsGITclientpluginv1.4.6GITClientforWindowsv1.8 .4(preview20130916) Description: Hi,IamexperiencingaproblemontheGITpollingandherearethedetails:WhentheoptionBranchestobuildonGITPluginforJenkinsisblankor**theGITpollingworkingjustfinebutwhenIenteredmasterororigin/masterorothertooptionBranchestobuildtheGITpollingcrasheswiththefollowingerror(seealso snapshot snapshots ):StartedonNov11,20131:15:13PMUsingstrategy:Default[poll]LastBuiltRevision:Revision1d530845b2467e9e342fbf19e101c1291e1458a9(origin/master)FATAL:Errorperformingcommand:ls-remote-hssh://g...@mymachine0005.us.mycompany.com:7999/LT/ltpc.gitmasterhudson.util.IOException2:Errorperformingcommand:ls-remote-hssh://g...@mymachine0005.us.mycompany.com:7999/LT/ltpc.gitmaster athudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:458) athudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) athudson.scm.SCM.poll(SCM.java:373) athudson.model.AbstractProject._poll(AbstractProject.java:1530) athudson.model.AbstractProject.poll(AbstractProject.java:1455) athudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) athudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) athudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource)Causedby:hudson.plugins.git.GitException:Errorperformingcommand:ls-remote-hssh://g...@mymachine0005.us.mycompany.com:7999/LT/ltpc.gitmaster atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:988) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:920) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.getHeadRev(CliGitAPIImpl.java:1297) athudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:488) athudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:456) ...13moreCausedby:java.io.IOException:Cannotrunprogramgit.exe:CreateProcesserror=2,Thesystemcannotfindthefilespecified atjava.lang.ProcessBuilder.start(UnknownSource) athudson.Proc$LocalProc.init(Proc.java:244) athudson.Proc$LocalProc.init(Proc.java:216) athudson.Launcher$LocalLauncher.launch(Launcher.java:773) athudson.Launcher$ProcStarter.start(Launcher.java:353) atorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:977) ...17moreCausedby:java.io.IOException:CreateProcesserror=2,Thesystemcannotfindthefilespecified atjava.lang.ProcessImpl.create(NativeMethod) atjava.lang.ProcessImpl.init(UnknownSource) atjava.lang.ProcessImpl.start(UnknownSource) ...23moreDone.Took0.37secNochangesAnyIdea?ThankYouforyoursupport,Ronen. 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Sega assigned JENKINS-10313 to Sega Fails to copy artifacts from one multi-configuration build to another Change By: Sega (31/May/13 4:05 AM) Assignee: Sega 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Sega assigned JENKINS-10313 to Unassigned Fails to copy artifacts from one multi-configuration build to another Change By: Sega (31/May/13 4:07 AM) Assignee: Sega 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Sega assigned JENKINS-10313 to Sega Fails to copy artifacts from one multi-configuration build to another Change By: Sega (31/May/13 4:07 AM) Assignee: Sega 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-10313) Fails to copy artifacts from one multi-configuration build to another
Sega assigned JENKINS-10313 to snrkiwi71 Fails to copy artifacts from one multi-configuration build to another Change By: Sega (31/May/13 4:07 AM) Assignee: Sega snrkiwi71 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/groups/opt_out.
[JIRA] [customtools-plugin] (JENKINS-14515) Malformed PATH environment variable on Windows slave (unix syntax used)
Sega commented on JENKINS-14515 Malformed PATH environment variable on Windows slave (unix syntax used) I have the same problem! On Windows slave and Jenkins installed on Linux O/S Path=D:\Jenkins\tools\Custom_tool\NodeJS-0.9.9:/var/lib/jenkins/D: ... 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/groups/opt_out.
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Sega edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, you are right. the full path need to be also for the "Class directory" and "Source directory" columns. I recommend you to add more error/debug messages with explanations, It's makes life easier for the end user troubleshooting. Ok now its working But now the "Coverage Breakdown by Module" and the total result tables graphics look weird (text exceeds the limit of the column). 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Sega edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data The Jacoco .exec file full structure path is: "target/jacoco/jacoco.exec". "jacoco.exec" file is in "module/target/jacoco" folder. 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Sega edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Thanks Ognjen One more question please: After the Jacoco plugin successfully finished to collect the modules data (*.exec) and the build successfully finished, I go back to my Jenkins Job - last Build - "Coverage Report" and on this screen all the column with 0.0% M:0 C: 0 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Sega commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Thanks Ognjen, You are doing a great job and great support! 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, you are right. the full path need to be also for the "Class directory" and "Source directory" columns. I recommend you to add more error/debug messages with explanations, It's makes life easier for the end user troubleshooting. Ok now its working But now the "Coverage Breakdown by Module" and the total result tables graphics look weird (text exceeds the limit of the column), take a look on this snapshot: http://192.117.122.51/Coverage_Summary.jpg. Maybe disable/enable option for Class/Module counter? 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Sega commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Yes, same thing in package and class. BTW: I tested it on IE9, FireFox and Chrome (same result). 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg
edited a comment on JENKINS-14896
java.io.FileNotFoundException when saving module data
Yes in every module there is direcotry called: "*/target/jacoco" including the "jacoco.exec" file ("*/target/jacoco/jacoco.exec"), I checked it.
For example let's take the "Wizard" module:
Full Jacoco path on slave machine: "C:\Jenkins\workspace\Continuous_Build\Platform\trunk\Application\Wizard\target\jacoco"
Full build path on master machine: "D:\Jenkins\jobs\Continuous_Build"
I also checked and the build without Jacoco Jenkins plugin is stable (fully succeed).
Deubg:
execfile = c:\Jenkins\workspace\Continuous_Build\target\jacoco\jacoco.exec
seged = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco\module0\jacoco.exec
actualBuildDirRoot = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco
actualBuildModuleDir = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco\module0
getWorkspace = c:\Jenkins\workspace\Continuous_Build
moduleName = Wizard
Please tell me if you need more information...
Thank You.
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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data I checked it and yes its working now! I had to enter the full path in each module. Tell me Ognjen, Are you planning to support **/ option in the "Exec file relative path" column? (For example: **/target/jacoco/jacoco.exec) Thank You 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Thanks Ognjen One more question please: After the Jacoco plugin successfully finished to collect the modules data (*.exec) and the build successfully finished, I go back to my Jenkins job - last build - "Coverage Report" and on this screen all the column with %0 M:0 C: 0, Why? The Console Log: JaCoCo plugin Reports added JaCoCo plugin Storing properties file.. JaCoCo plugin Loading EXEC files.. JaCoCo plugin Publishing the results.. JaCoCo plugin Loading module: . . . 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Thanks Ognjen One more question please: After the Jacoco plugin successfully finished to collect the modules data (*.exec) and the build successfully finished, I go back to my Jenkins Job - last Build - "Coverage Report" and on this screen all the column with 0.0% M:0 C: 0 (See snapshot: http://192.117.122.51/coverage_empty.jpg), Why? What am I missing? The Console Log: JaCoCo plugin Reports added JaCoCo plugin Storing properties file.. JaCoCo plugin Loading EXEC files.. JaCoCo plugin Publishing the results.. JaCoCo plugin Loading module: . . . 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, you are right. the full path need to be also for the "Class directory" and "Source directory" columns. Ok now its working, but now the total result and the "Coverage Breakdown by Module" table graphics look weird, take a look on this snapshot: "http://192.117.122.51/Coverage_Summary.jpg" 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, you are right. the full path need to be also for the "Class directory" and "Source directory" columns. I recommend you to add more error/debug messages with explanations, It's makes life easier for the end user troubleshooting. Ok now its working But now the "Coverage Breakdown by Module" and the total result tables graphics look weird (text exceeds the limit of the column), take a look on this snapshot: http://192.117.122.51/Coverage_Summary.jpg. 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Thank You, I'm waitting for the new update 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Thank You! The new update is now available in Jenkins. I'm checking it now... 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Once again... Failure For some unknown reason the Jacoco plugin trying to copy "jacoco.exec" from root\target folder, there is no "TARGET" folder under the root folder (c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec). Master: D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_12-06-11\jacoco\module0\jacoco.exec Slave: c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec OUTPUT LOG: JaCoCo plugin Saving module data.. ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception hudson.util.IOException2: Failed to copy c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec to D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_12-06-11\jacoco\module0\jacoco.exec at hudson.FilePath.copyTo(FilePath.java:1573) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:143) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1513) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.util.IOException2: remote file operation failed: c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec at hudson.remoting.Channel@65cc33:TEST_VM2_WIN2K8_X64 at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.copyTo(FilePath.java:1594) at hudson.FilePath.copyTo(FilePath.java:1568) ... 10 more Caused by: java.io.FileNotFoundException: c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec (The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:138) at hudson.FilePath$33.invoke(FilePath.java:1599) at hudson.FilePath$33.invoke(FilePath.java:1594) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Once again... Build Failure, same issue For some unknown reason the Jacoco plugin trying to copy "jacoco.exec" from root\target folder, there is no "TARGET" folder under the root folder (c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec). Master: D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_12-06-11\jacoco\module0\jacoco.exec Slave: c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec Jenkins Version: 1.476 Jacoco plugin version: 1.0.4 OUTPUT LOG: JaCoCo plugin Saving module data.. ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception hudson.util.IOException2: Failed to copy c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec to D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_12-06-11\jacoco\module0\jacoco.exec at hudson.FilePath.copyTo(FilePath.java:1573) at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:143) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1513) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: hudson.util.IOException2: remote file operation failed: c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec at hudson.remoting.Channel@65cc33:TEST_VM2_WIN2K8_X64 at hudson.FilePath.act(FilePath.java:838) at hudson.FilePath.act(FilePath.java:824) at hudson.FilePath.copyTo(FilePath.java:1594) at hudson.FilePath.copyTo(FilePath.java:1568) ... 10 more Caused by: java.io.FileNotFoundException: c:\Jenkins\workspace\Continuous_Build\target\jacoco.exec (The system cannot find the path specified) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:138) at hudson.FilePath$33.invoke(FilePath.java:1599) at hudson.FilePath$33.invoke(FilePath.java:1594) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2196) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data From my Jenkins system: http://192.117.122.51/JaCoCo1.jpg 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data The Jacoco .exec file full structure path is: "target/jacoco/jacoco.exec". "jacoco.exec" file is in "module/target/jacoco" folder. Here is screenshot: http://192.117.122.51/JaCoCo1.jpg 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, this is another project but with the same issue, here is the informaation about this project: ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception hudson.util.IOException2: Failed to copy c:\Jenkins\workspace\Continuous_Build\target\jacoco\jacoco.exec to D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_16-30-20\jacoco\module0\jacoco.exec The folder: "c:\Jenkins\workspace\Continuous_Build\target\jacoco\target" doesn't exist. The file "D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_16-30-20\jacoco\module0\jacoco.exec" exist but with 0 bytes. Thank You 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, this is another project but with the same issue, here is the informaation about this project: JaCoCo plugin ConfigRow moduleName=WizardsrcDir=src, classDir=target/classes, execFile=target/jacoco/jacoco.exec locations are configured . . . JaCoCo plugin Saving module data... ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception hudson.util.IOException2: Failed to copy c:\Jenkins\workspace\Continuous_Build\target\jacoco\jacoco.exec to D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_16-30-20\jacoco\module0\jacoco.exec The folder: "c:\Jenkins\workspace\Continuous_Build\target\jacoco\target" doesn't exist. The file "D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_16-30-20\jacoco\module0\jacoco.exec" exist but with 0 bytes. Thank You 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yep, this is another project but with the same issue, here is the informaation about this project: JaCoCo plugin ConfigRow moduleName=WizardsrcDir=src, classDir=target/classes, execFile=target/jacoco/jacoco.exec locations are configured . . . JaCoCo plugin Saving module data... ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception hudson.util.IOException2: Failed to copy c:\Jenkins\workspace\Continuous_Build\target\jacoco\jacoco.exec to D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_16-30-20\jacoco\module0\jacoco.exec . . . Please note that, the folder: "c:\Jenkins\workspace\Continuous_Build\target\jacoco\target" doesn't exist. And the file "D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_16-30-20\jacoco\module0\jacoco.exec" exist but with 0 bytes. Thank You 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg
edited a comment on JENKINS-14896
java.io.FileNotFoundException when saving module data
Yes in every module there is direcotry called: "*/target/jacoco" including the "jacoco.exec" file ("*/target/jacoco/jacoco.exec"), I checked it.
For example let's take the "Wizard" module:
Full Jacoco path on slave machine: "C:\Jenkins\workspace\Continuous_Build\Platform\trunk\Application\Wizard\target\jacoco"
Full build path on master machine: "D:\Jenkins\jobs\Continuous_Build"
I also checked and the build without Jacoco Jenkins plugin is stable (fully succeed).
Deubg:
execfile = c:\Jenkins\workspace\Continuous_Build\target\jacoco\jacoco.exec
actualBuildDirRoot = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco
actualBuildModuleDir = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco\module0
getWorkspace = c:\Jenkins\workspace\Continuous_Build
Please tell me if you need more information...
Thank You.
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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg
edited a comment on JENKINS-14896
java.io.FileNotFoundException when saving module data
Yes in every module there is direcotry called: "*/target/jacoco" including the "jacoco.exec" file ("*/target/jacoco/jacoco.exec"), I checked it.
For example let's take the "Wizard" module:
Full Jacoco path on slave machine: "C:\Jenkins\workspace\Continuous_Build\Platform\trunk\Application\Wizard\target\jacoco"
Full build path on master machine: "D:\Jenkins\jobs\Continuous_Build"
I also checked and the build without Jacoco Jenkins plugin is stable (fully succeed).
Deubg:
execfile = c:\Jenkins\workspace\Continuous_Build\target\jacoco\jacoco.exec
seged = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco\module0\jacoco.exec
actualBuildDirRoot = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco
actualBuildModuleDir = D:\Jenkins\jobs\Continuous_Build\builds\2012-09-04_XX-XX-XX\jacoco\module0
getWorkspace = c:\Jenkins\workspace\Continuous_Build
Please tell me if you need more information...
Thank You.
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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yes, I'm facing the same BUG! ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception hudson.util.IOException2: Failed to copy D:\Jenkins\jobs\\workspace\target\jacoco.exec to D:\Jenkins\jobs\\builds\2012-08-28_18-49-28\jacoco\module0\jacoco.exec Why Jacoco plugin want to copy the "jacoco.exec" from the "workspace\target folder"? note that, there is no "workspace\target" folder. Jenkins version: 1.476 Jenkins Jacoco plugin version: 1.0.3 BTW: I ran this job on slave and master, I'm getting the same problem! Thanks. 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg edited a comment on JENKINS-14896 java.io.FileNotFoundException when saving module data Yes, I'm facing the same BUG! ERROR: Publisher hudson.plugins.jacoco.JacocoPublisher aborted due to exception hudson.util.IOException2: Failed to copy D:\Jenkins\jobs\\workspace\target\jacoco.exec to D:\Jenkins\jobs\\builds\2012-08-28_18-49-28\jacoco\module0\jacoco.exec Why Jacoco plugin want to copy the "jacoco.exec" from the "workspace\target folder"? note that, there is no "workspace\target" folder. Jenkins version: 1.476 Jenkins Jacoco plugin version: 1.0.3 BTW: I checked this issue on slave and master machines and I'm getting the same problem! Thanks. 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
[JIRA] (JENKINS-14896) java.io.FileNotFoundException when saving module data
Ronen Peleg commented on JENKINS-14896 java.io.FileNotFoundException when saving module data As I wrote in my last comment, I already tried it on the same machine (master only, without slave) and I'm getting the same problem. 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
[JIRA] (JENKINS-14274) Multi module reporting
Ronen Peleg commented on JENKINS-14274 Multi module reporting As you know the Jenkins Jacoco plugin still doesn't support "Multi module reporting", using "jacoco:report" will create you only the last module. If I understand you correctly, you tried to create one exec file that containing all coverage data from all module project, its good idea but still the jenkins plugin will create report only for the last module. To make it work you must to attach the module classes to the jacoco directory when running jacoco report. Note that, the best practice is to create the jacoco.exec for each target directory. You can use temporary solution using ant task: http://java.dzone.com/articles/jacoco-maven-multi-module 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
[JIRA] (JENKINS-14274) Multi module reporting
Ronen Peleg edited a comment on JENKINS-14274 Multi module reporting As you know the Jenkins Jacoco plugin still doesn't support "Multi module reporting", using "jacoco:report" will create you only the last module. If I understand you correctly, you tried to create one exec file that containing all coverage data from all module project, its good idea but still the jenkins plugin will create report only for the last module. To make it work you must to attach the module classes to the jacoco directory when running jacoco report. Note that, the best practice is to create the jacoco.exec for each target directory. Until we have a multi module reporting implemented in Jenkins Jacoco plugin, you can use the following temporary solution using Ant task: http://java.dzone.com/articles/jacoco-maven-multi-module 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
[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Ronen Peleg resolved JENKINS-14474 as Fixed Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk Update to Jenkins 1.4.75+ to solve this issue. Change By: Ronen Peleg (06/Aug/12 3:38 AM) Status: Open Resolved Assignee: RonenPeleg Resolution: Fixed 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
[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Ronen Peleg commented on JENKINS-14474 Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk Maybe your old jobs requests for plugins that not including in your new Jenkins system. Check and make sure that you have the same system settings and plugins like in you had in the old Jenkins system. 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
[JIRA] (JENKINS-14474) Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk
Ronen Peleg edited a comment on JENKINS-14474 Multi-configuration jobs disappear from the list when Jenkins configuration is reloaded from disk Maybe your old multi-config jobs requests for plugins that not including (exist) in your NEW Jenkins system. Check and make sure that you have the same system settings and plugins like in you had in the old Jenkins system. 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
