Combine one or more Trigger conditions
I have created a jenkins build that runs every @midnight but I wanna run this build at every midnight and also change is push to repo so How can I check every midnight, whether change is pushed or not? Thanks. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Running a shell command on multiple/all slaves from script console
Am 12.12.2013 10:33, schrieb Omer Weissman: I want to execute an administrative shell script on all slaves using the script console in Jenkins manage. Did you try the Debian distributed shell (dsh)? HTH... Dirk -- *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach *Tel*: +49 2226 159 (Ansage) 1149 *Email*: d...@recommind.com mailto:d...@recommind.com *Skype*: dirk.heinrichs.recommind www.recommind.com http://www.recommind.com http://www.recommind.com -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. inline: Logo.gif
Re: Getting OutOfMemoryError (OOM) constantly in latest update to 1.542.
So this is what is happening for us : - The build-usage plugin was displaying the problems at the beginning of the thread, so we disabled it. - Now, every build that we do, and every sub-project fills up the 'Old data' log, with hundreds of CannotResolveClassException: hudson.plugins.disk_usage.BuildDiskUsageAction even though that plugin is not used in that build, and does not exist any more. After a modest number of builds (say, 1/2 a day or so), Jenkins bombs with OOM as this log is filled with *millions* of entries, and it's game over. Is there a way to disable this functionality? I can't see the utility of it, and it's making the system totally unusable. On Wed, Dec 11, 2013 at 5:55 PM, Nigel Magnay nigel.mag...@gmail.comwrote: I've just cracked out MAT on a oom dump from our machine, and I can confirm that it looks like OldDataMonitor is the culprit here, too (750Mb of retained heap). There's over a million entries in the hashmap... On Mon, Dec 9, 2013 at 4:32 PM, Tim Drury tdr...@gmail.com wrote: I'm doing a heap-dump analysis now and I think I might know what the issue was. The start of this whole problem was the disk-usage plugin hanging our attempts to view a job in Jenkins (see https://issues.jenkins-ci.org/browse/JENKINS-20876) so we disabled that plugin. After disabling, Jenkins complained about data in an older/unreadable format: You have data stored in an older format and/or unreadable data. If I click the Manage button to delete it, it takes a _long_ time for it to display all the disk-usage plugin data - there must be thousands of rows, but it does display it all eventually. The error shown in each row is: CannotResolveClassException: hudson.plugins.disk_usage.BuildDiskUsageAction If I click Discard Unreadable Data at the bottom of the page, I quickly get a stack trace: javax.servlet.ServletException: java.util.ConcurrentModificationException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:587) at org.kohsuke.stapler.Stapler.service(Stapler.java:218) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) and it fails to discard the data. Older data isn't usually a problem so I brushed off this error. However, here is dominator_tree of the heap dump: Class Name | Shallow Heap | Retained Heap | Percentage hudson.diagnosis.OldDataMonitor @ 0x6f9f2c4a0 | 24 | 3,278,466,984 | 88.69% com.thoughtworks.xstream.converters.SingleValueConverterWrapper @ 0x6f9da8780 | 16 | 13,825,616 | 0.37% hudson.model.Hudson @ 0x6f9b8b8e8 | 272 | 3,572,400 | 0.10% org.eclipse.jetty.webapp.WebAppClassLoader @ 0x6f9a73598 | 88 | 2,308,760 | 0.06% org.apache.commons.jexl.util.introspection.Introspector @ 0x6fbb74710 | 32 | 1,842,392 | 0.05% org.kohsuke.stapler.WebApp @ 0x6f9c0ff10 | 64 | 1,127,480 | 0.03% java.lang.Thread @ 0x7d5c2d138 Handling GET /view/Alle/job/common-translation-main/ : RequestHandlerThread[#105] Thread| 112 | 971,336 | 0.03% What is hudson.diagnosis.OldDataMonitor? Could the disk-usage plugin data be the cause of all my recent OOM errors? If so, how do I get rid of it? -tim On Monday, December 9, 2013 9:41:25 AM UTC-5, Tim Drury wrote: I intended to install 1.532 on Friday, but mistakenly installed 1.539. It gave us the same OOM exceptions.
RE: Combine one or more Trigger conditions
When you configure a job, you can select multiple build triggers. You want a build periodically trigger (@midnight) and a Poll SCM trigger. --Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Erol KOCAMAN Sent: Thursday, December 12, 2013 3:46 AM To: jenkinsci-users@googlegroups.com Subject: Combine one or more Trigger conditions I have created a jenkins build that runs every @midnight but I wanna run this build at every midnight and also change is push to repo so How can I check every midnight, whether change is pushed or not? Thanks. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
--sessionTimeout and/or Remember me on the computer
As many people in the posts I have read on various internet sites have indicated, Jenkins session timing out is a great annoyance. I have read about a hack to the web.xml, the Bind DN and a couple of other fixes. I also see that 1.528 supports: - Command line now supports --sessionTimeout option for controlling session timeout How, exactly, would I use this? What is the command? Is it just for the session your in (and would therefore need to be run each time you open up Jenkins)? I appreciate your patience with this question. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Getting OutOfMemoryError (OOM) constantly in latest update to 1.542.
I had some success getting the Manage Old Data screen to work. Most of the time it will throw a ConcurrentModificationException, but occasionally it will list a few hundred records with the Discard Old Data button. I press the button and - again - sometimes it will work and sometimes throw a CME, but in either case it does seem to delete some of the old data. I repeated this process about every hour a couple days ago and managed to delete enough old data that Jenkins continued to run for more than a day. The best chance of this working is when no build jobs are running. The alternative is to manually delete the disk-usage XML elements from the build.xml files in each job's build directories. I did this for about 200 files before I got tired of doing it. A groovy script could probably be written to do this. -tim On Thursday, December 12, 2013 5:26:42 AM UTC-5, nigelm wrote: So this is what is happening for us : - The build-usage plugin was displaying the problems at the beginning of the thread, so we disabled it. - Now, every build that we do, and every sub-project fills up the 'Old data' log, with hundreds of CannotResolveClassException: hudson.plugins.disk_usage.BuildDiskUsageAction even though that plugin is not used in that build, and does not exist any more. After a modest number of builds (say, 1/2 a day or so), Jenkins bombs with OOM as this log is filled with *millions* of entries, and it's game over. Is there a way to disable this functionality? I can't see the utility of it, and it's making the system totally unusable. On Wed, Dec 11, 2013 at 5:55 PM, Nigel Magnay nigel@gmail.comjavascript: wrote: I've just cracked out MAT on a oom dump from our machine, and I can confirm that it looks like OldDataMonitor is the culprit here, too (750Mb of retained heap). There's over a million entries in the hashmap... On Mon, Dec 9, 2013 at 4:32 PM, Tim Drury tdr...@gmail.com javascript: wrote: I'm doing a heap-dump analysis now and I think I might know what the issue was. The start of this whole problem was the disk-usage plugin hanging our attempts to view a job in Jenkins (see https://issues.jenkins-ci.org/browse/JENKINS-20876) so we disabled that plugin. After disabling, Jenkins complained about data in an older/unreadable format: You have data stored in an older format and/or unreadable data. If I click the Manage button to delete it, it takes a _long_ time for it to display all the disk-usage plugin data - there must be thousands of rows, but it does display it all eventually. The error shown in each row is: CannotResolveClassException: hudson.plugins.disk_usage.BuildDiskUsageAction If I click Discard Unreadable Data at the bottom of the page, I quickly get a stack trace: javax.servlet.ServletException: java.util.ConcurrentModificationException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:587) at org.kohsuke.stapler.Stapler.service(Stapler.java:218) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) and it fails to discard the data. Older data isn't usually a problem so I brushed off this error. However, here is dominator_tree of the heap dump: Class Name | Shallow Heap | Retained Heap | Percentage hudson.diagnosis.OldDataMonitor @ 0x6f9f2c4a0 | 24 | 3,278,466,984 | 88.69% com.thoughtworks.xstream.converters.SingleValueConverterWrapper @ 0x6f9da8780 | 16 | 13,825,616 | 0.37% hudson.model.Hudson @ 0x6f9b8b8e8 | 272 | 3,572,400 |
How to turn off looking up the previous build?
I have a Jenkins job which can get triggered in a variety of ways, either via SCM polling or via a Gerrit trigger. The order in which the jobs are run has no real relationship to the ordering of the commits being built, so comparing the current build with the previous build is not very useful. In addition, attempting to retrieve the commit hash of a previous build may fail, as the current workspace may not actually contain the ref of the previous build. I would like to turn off that feature. How can I do that? Using Jenkins 1.542 and the git plugin 2.0. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[chef] Minitest
Hi Chefs, I am experiencing a problem with the order that minitest is running. Does exist a way to say to minitest run in a desired order? Atenciosamente, Eduardo -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Build-Flow graph disappeared after restart jenkins
We had a similar problem upgrading to LTS 1.504.9. Part of it was upgrading the buildflow plugin. We reverted to version 0.9 for now, till they fix a bug. So waiting for that release to upgrade. br/Frank On Thursday, December 12, 2013 6:20:54 AM UTC-8, zacky az wrote: Hi, After restart Jenkins or Reload Configuration from Disk Build-Flow graph disappeared Jenkins ver. 1.542 on SUSE Linux Enterprise Server 11 SP2 (x86_64) buildgraph-view 1.1.1 CloudBees Build Flow plugin 0.10 Can you please let me know what i am doing wrong Regards Zacky -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
