Jenkins is telling me that I have too many threads stuck. On Tuesday, February 16, 2016 at 2:48:56 PM UTC-6, John Mellor wrote: > > Hector stated: > > Ø I tried polling with a schedule like H/10 * * * * which means "every > 10 minutes". But polling doesn't seem to work. > > > > H/10 * * * * should give you a pooling cycle of about every 6 minutes, not > 10. I use something similar because my current git repo does not allow me > to insert a hook script. It works correctly, so I suspect your build > triggering problem is elsewhere. > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *Hector Magnanao > *Sent:* February-16-16 15:43 > *To:* Jenkins Users > *Cc:* [email protected] <javascript:> > *Subject:* Re: Polling in Jenkins > > > > I tried polling with a schedule like H/10 * * * * which means "every 10 > minutes". But polling doesn't seem to work. > > > > How can I setup a post-commit hook to notify Jenkins of checkins. ? > > > > > > On Tuesday, February 16, 2016 at 12:26:58 PM UTC-6, Daniel Beck wrote: > > If you're polling, you need to define a schedule -- Jenkins needs to know > how often to poll, after all. This can be as simple as '* * * * *', which > means "every minute". > > Consider looking into (SCM specific) post-commit hooks, those notify > Jenkins of changes immediately, and don't require Jenkins to poll all the > time (which as you can imagine, doesn't scale well). > > On 16.02.2016, at 19:06, Hector Magnanao <[email protected]> wrote: > > > I'm using Jenkins 1.625.2 > > > > How do I setup polling in Jenkins so that my build will execute whenever > a file is checked in ? I tried to setup polling but when I choose Poll SCM, > it asked for a schedule. Do I have to put in a schedule or is there a way > to setup polling without schedule ? I want my build to execute whenever a > file is checked in. > > > > -- > > 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 [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/533d2bd1-f12b-44d9-9f66-bd137910f9dc%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. > > -- > 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 [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/ecdcdccb-511a-4b9a-9e2b-481b53e14dd8%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-users/ecdcdccb-511a-4b9a-9e2b-481b53e14dd8%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. >
-- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e6ca4c46-5b9e-4b21-998a-66b90e41dedc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
