I believe you are mistaken.
Certainly in a crontab, the following are identical:
*/30 * * * *
0,30 * * * *
I want this to trigger every half hour, 11:00 and 11:30 were just examples.
Furthermore, the above is for *polling* subversion for changes, not
building the job regardless, so no, it is not a 'period job'.
cheers,
Chris
On 07/06/2013 02:52, Xiaopan Bao 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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
