Hi,
I did a test of the Quartz scheduler library we use and it doesn't seem to support that kind of cron expression, it just silently doesn't interpret it correctly, and it's not clear how it does interpret it.
I tested against a newer version of quartz and received this error message: "Support for specifying multiple "nth" days is not imlemented" (sic)
So it appears that it is not possible to do in a single scheduled job, I'm sorry to say. I guess you could either use a different cron expression to get a similar effect if necessary, or have two top-level jobs which use Job references to the actual you job you want to run, and apply each part of the cron schedule to the top-level jobs.
On Mon, Oct 29, 2012 at 6:51 AM, SirHopcount
<adrianv...@gmail.com> wrote:
Hi,
I have a small question about the con schedule in Rundeck. I am trying to create a job thats runs every first and every third Tuesday of the month. I have read the cron reference and have created a cron expressions to should match this:
0 00 05 ? * 2#1,2#3 *
As far as I can tell this syntax should be correct but for some reason Rundeck only takes the last "day of the week" value. If if create a job with a cron like this:
0 00 05 ? * 2#1 *
Rundeck informs me its going to run in 6 days, which is correct because I want the first Tuesday of the month. But when I add ,2#3 to add the third Tuesday Rundeck informs me the next run will be in 20 days. For some reason it no longer sees the first Tuesday.
Question is, is there something wrong with my syntax ?
Regards,
Hopcount.