Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
Greetings,
I have a use-case where I need to schedule a build to occur every 1.5 hours from 06:00-23:00, and I don't think that can reasonably be done with a single cron expression -- Is it possible to provide multiple cron expressions to cover this scenario? Something like this?
[list]
0 30 7-23/3 * * *[/*:m][/list:u]
If this is not currently possible, is this something that you would consider accepting an improvement request for? And is it something minor enough that it could fit in the next few patches?
Thanks,
-J. Mash
-
replies
3
-
views
1863
-
stars
0
-
Sorry we will not add this improvement as this edge case can be handled by creating two different configurations each with different cron schedule and have it triggering your desired configuration.
Hmm... That seems a rather ugly solution to me, actually.
It will nearly double the number of top-level configurations required for this project, and that will ultimately make the dashboard's visualization very noisy and confusing. Which configuration is to be used to kick of an extra, manual build? Does it matter? If it doesn't matter, then builds now get triggered under either configuration with reckless abandon, and we no longer have a single location where I can go to see the entire build history of scheduled and triggered builds. Unless, of course, wrapper configurations are created for each cron job that invoke the original configuration to do the work, but then you're talking about tripling the number of configurations to make this work.
It may be an edge case, but the proposed workaround presents significant enough drawbacks /ugliness that the more palatable "solution" is to just build every 2 hours. Both are less than ideal, however.
Thanks,
-J. Mash
Unfortunately under current architecture, it is not possible to use multiple cron exressions with a single configuration as configuration schedule is solely managed by a single quartz trigger.
