But if you use periodic job trigger, it will run even if there are no changes to the code.
I have the same problem -- polling and the job used to happen at the time I had set. Now there appears to be a delay. I want it to run at a specific time but only if there were code changes so I need to use the polling trigger, not the periodic trigger. On Thu, Jun 6, 2013 at 6:52 PM, Xiaopan Bao <[email protected]> wrote: > because you set a wrong format... > if you want to expect the job trigger exactly at 11:00 and 11:30, it > should not be called "polls job", it should be called "period job"... > you can set as following: > 0,30 11 * * * > > 在 2013年6月6日星期四UTC+8下午6时46分21秒，Chris Withers写道： >> >> Hi All, >> >> I have a job that polls svn as follows: >> >> */30 * * * * >> >> ...yet the job kicked off at 11:09:02. I would expect the job to trigger >> at 11:00 or 11:30 but not 11:09. >> >> What could cause that 9 minute lag? >> >> Chris >> >> -- >> Simplistix - Content Management, Batch Processing & Python Consulting >> - http://www.simplistix.co.uk >> > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
