[feature request]support parameter “H” like which in Jenkins

[iambocai]

For example, using 0 0 * * * for a dozen daily jobs will cause a large spike at midnight. In contrast, using H H * * * would still execute each job once a day, but not all at the same time, better using limited resources.

The H symbol can be thought of as a random value over a range, but it actually is a hash of the job name, not a random function, so that the value remains stable for any given project.

To allow periodically scheduled tasks to produce even load on the system, the symbol H (for “hash”) should be used wherever possible.

[jhuckaby]

Holy crap, this is a WONDERFUL idea. I absolutely love it. I will implement this in the next version without fail.

Thank you!!!

[jhuckaby]

Implemented in v0.6.4. Thanks again! https://github.com/jhuckaby/Cronicle/releases/tag/v0.6.4

[iambocai]

Can we support steps after H?

It acts just like step after *, but will add a specific step size, this helps to avoid the server in the first few seconds of every minute very busy, for example:
*/5 * * * * ---> run when minute %5 == 0 && second == 0
h/5 * * * * ---> run when minute %5 == hash(job_id, 0, 5) && second == hash(job_id, 0, 60)
h * * * * ---> run when every minute && second == hash(job_id, 0, 60)