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 n
On 07/06/2013 17:02, Phillip Campbell wrote:
I am sorry, I guess we have not explained the problem correctly. It is
not the build time that is the problem, it is the polling time.
I have my job set to poll every night at 9pm (21h) yet the Subversion
Polling Log (not the build time) shows that t
I am sorry, I guess we have not explained the problem correctly. It is not
the build time that is the problem, it is the polling time.
I have my job set to poll every night at 9pm (21h) yet the Subversion
Polling Log (not the build time) shows that the polling did not occur until
9:09pm - nine mi
Use
0,30 11 * * *
as suggested by Xiaopan Bao, but keep it as a polling job. That will check
at those specific times, and queue a build if there have been changes. I'm
not sure how different that is to */30 (maybe 0,30='at 0 and 30' versus
*/30='every 30 minutes starting at an arbitrary poin
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 us
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 po
One possibility is that the job was queued at 11:00 but did not get a
free executor until 11:09.
Eric
On 6/6/2013 6:46 AM, Chris Withers wrote:
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
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
