cron
packagemoduleThis package is not in the latest version of its module.
Details
Validgo.mod file
The Go module system was introduced in Go 1.11 and is the official dependency management solution for Go.
Redistributable license
Redistributable licenses place minimal restrictions on how software can be used, modified, and redistributed.
Tagged version
Modules with tagged versions give importers more predictable builds.
Stable version
When a project reaches major version v1 it is considered stable.
- Learn more about best practices
Repository
Links
README¶
cron
Cron V3 has been released!
To download the specific tagged release, run:
go get github.com/robfig/cron/v3@v3.0.0
Import it in your program as:
import "github.com/robfig/cron/v3"
It requires Go 1.11 or later due to usage of Go Modules.
Refer to the documentation here:http://godoc.org/github.com/robfig/cron
The rest of this document describes the the advances in v3 and a list ofbreaking changes for users that wish to upgrade from an earlier version.
Upgrading to v3 (June 2019)
cron v3 is a major upgrade to the library that addresses all outstanding bugs,feature requests, and rough edges. It is based on a merge of master whichcontains various fixes to issues found over the years and the v2 branch whichcontains some backwards-incompatible features like the ability to remove cronjobs. In addition, v3 adds support for Go Modules, cleans up rough edges likethe timezone support, and fixes a number of bugs.
New features:
Support for Go modules. Callers must now import this library as
github.com/robfig/cron/v3
, instead ofgopkg.in/...
Fixed bugs:
- 0f01e6b parser: fix combining of Dow and Dom (#70)
- dbf3220 adjust times when rolling the clock forward to handle non-existent midnight (#157)
- eeecf15 spec_test.go: ensure an error is returned on 0 increment (#144)
- 70971dc cron.Entries(): update request for snapshot to include a reply channel (#97)
- 1cba5e6 cron: fix: removing a job causes the next scheduled job to run too late (#206)
Standard cron spec parsing by default (first field is "minute"), with an easyway to opt into the seconds field (quartz-compatible). Although, note that theyear field (optional in Quartz) is not supported.
Extensible, key/value logging via an interface that complies withthehttps://github.com/go-logr/logr project.
The new Chain & JobWrapper types allow you to install "interceptors" to addcross-cutting behavior like the following:
- Recover any panics from jobs
- Delay a job's execution if the previous run hasn't completed yet
- Skip a job's execution if the previous run hasn't completed yet
- Log each job's invocations
- Notification when jobs are completed
It is backwards incompatible with both v1 and v2. These updates are required:
The v1 branch accepted an optional seconds field at the beginning of the cronspec. This is non-standard and has led to a lot of confusion. The new defaultparser conforms to the standard as described bythe Cron wikipedia page.
UPDATING: To retain the old behavior, construct your Cron with a customparser:
// Seconds field, requiredcron.New(cron.WithSeconds())// Seconds field, optionalcron.New( cron.WithParser( cron.SecondOptional | cron.Minute | cron.Hour | cron.Dom | cron.Month | cron.Dow | cron.Descriptor))
The Cron type now accepts functional options on construction rather than theprevious ad-hoc behavior modification mechanisms (setting a field, calling a setter).
UPDATING: Code that sets Cron.ErrorLogger or calls Cron.SetLocation must beupdated to provide those values on construction.
CRON_TZ is now the recommended way to specify the timezone of a singleschedule, which is sanctioned by the specification. The legacy "TZ=" prefixwill continue to be supported since it is unambiguous and easy to do so.
UPDATING: No update is required.
By default, cron will no longer recover panics in jobs that it runs.Recovering can be surprising (see issue #192) and seems to be at odds withtypical behavior of libraries. Relatedly, the
cron.WithPanicLogger
optionhas been removed to accommodate the more general JobWrapper type.UPDATING: To opt into panic recovery and configure the panic logger:
cron.New(cron.WithChain( cron.Recover(logger), // or use cron.DefaultLogger))
In adding support forhttps://github.com/go-logr/logr,
cron.WithVerboseLogger
wasremoved, since it is duplicative with the leveled logging.UPDATING: Callers should use
WithLogger
and specify a logger that does notdiscardInfo
logs. For convenience, one is provided that wraps*log.Logger
:cron.New( cron.WithLogger(cron.VerbosePrintfLogger(logger)))
Background - Cron spec format
There are two cron spec formats in common usage:
The "standard" cron format, described onthe Cron wikipedia page and used bythe cron Linux system utility.
The cron format used bythe Quartz Scheduler, commonly used for scheduledjobs in Java software
The original version of this package included an optional "seconds" field, whichmade it incompatible with both of these formats. Now, the "standard" format isthe default format accepted, and the Quartz format is opt-in.
Documentation¶
Overview¶
Package cron implements a cron spec parser and job runner.
Installation¶
To download the specific tagged release, run:
go get github.com/robfig/cron/v3@v3.0.0
Import it in your program as:
import "github.com/robfig/cron/v3"
It requires Go 1.11 or later due to usage of Go Modules.
Usage¶
Callers may register Funcs to be invoked on a given schedule. Cron will runthem in their own goroutines.
c := cron.New()c.AddFunc("30 * * * *", func() { fmt.Println("Every hour on the half hour") })c.AddFunc("30 3-6,20-23 * * *", func() { fmt.Println(".. in the range 3-6am, 8-11pm") })c.AddFunc("CRON_TZ=Asia/Tokyo 30 04 * * *", func() { fmt.Println("Runs at 04:30 Tokyo time every day") })c.AddFunc("@hourly", func() { fmt.Println("Every hour, starting an hour from now") })c.AddFunc("@every 1h30m", func() { fmt.Println("Every hour thirty, starting an hour thirty from now") })c.Start()..// Funcs are invoked in their own goroutine, asynchronously....// Funcs may also be added to a running Cronc.AddFunc("@daily", func() { fmt.Println("Every day") })..// Inspect the cron job entries' next and previous run times.inspect(c.Entries())..c.Stop() // Stop the scheduler (does not stop any jobs already running).
CRON Expression Format¶
A cron expression represents a set of times, using 5 space-separated fields.
Field name | Mandatory? | Allowed values | Allowed special characters---------- | ---------- | -------------- | --------------------------Minutes | Yes | 0-59 | * / , -Hours | Yes | 0-23 | * / , -Day of month | Yes | 1-31 | * / , - ?Month | Yes | 1-12 or JAN-DEC | * / , -Day of week | Yes | 0-6 or SUN-SAT | * / , - ?
Month and Day-of-week field values are case insensitive. "SUN", "Sun", and"sun" are equally accepted.
The specific interpretation of the format is based on the Cron Wikipedia page:https://en.wikipedia.org/wiki/Cron
Alternative Formats¶
Alternative Cron expression formats support other fields like seconds. You canimplement that by creating a custom Parser as follows.
cron.New(cron.WithParser(cron.NewParser(cron.SecondOptional | cron.Minute | cron.Hour | cron.Dom | cron.Month | cron.Dow | cron.Descriptor)))
Since adding Seconds is the most common modification to the standard cron spec,cron provides a builtin function to do that, which is equivalent to the customparser you saw earlier, except that its seconds field is REQUIRED:
cron.New(cron.WithSeconds())
That emulates Quartz, the most popular alternative Cron schedule format:http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/crontrigger.html
Special Characters¶
Asterisk ( * )
The asterisk indicates that the cron expression will match for all values of thefield; e.g., using an asterisk in the 5th field (month) would indicate everymonth.
Slash ( / )
Slashes are used to describe increments of ranges. For example 3-59/15 in the1st field (minutes) would indicate the 3rd minute of the hour and every 15minutes thereafter. The form "*\/..." is equivalent to the form "first-last/...",that is, an increment over the largest possible range of the field. The form"N/..." is accepted as meaning "N-MAX/...", that is, starting at N, use theincrement until the end of that specific range. It does not wrap around.
Comma ( , )
Commas are used to separate items of a list. For example, using "MON,WED,FRI" inthe 5th field (day of week) would mean Mondays, Wednesdays and Fridays.
Hyphen ( - )
Hyphens are used to define ranges. For example, 9-17 would indicate everyhour between 9am and 5pm inclusive.
Question mark ( ? )
Question mark may be used instead of '*' for leaving either day-of-month orday-of-week blank.
Predefined schedules¶
You may use one of several pre-defined schedules in place of a cron expression.
Entry | Description | Equivalent To----- | ----------- | -------------@yearly (or @annually) | Run once a year, midnight, Jan. 1st | 0 0 1 1 *@monthly | Run once a month, midnight, first of month | 0 0 1 * *@weekly | Run once a week, midnight between Sat/Sun | 0 0 * * 0@daily (or @midnight) | Run once a day, midnight | 0 0 * * *@hourly | Run once an hour, beginning of hour | 0 * * * *
Intervals¶
You may also schedule a job to execute at fixed intervals, starting at the time it's addedor cron is run. This is supported by formatting the cron spec like this:
@every <duration>
where "duration" is a string accepted by time.ParseDuration(http://golang.org/pkg/time/#ParseDuration).
For example, "@every 1h30m10s" would indicate a schedule that activates after1 hour, 30 minutes, 10 seconds, and then every interval after that.
Note: The interval does not take the job runtime into account. For example,if a job takes 3 minutes to run, and it is scheduled to run every 5 minutes,it will have only 2 minutes of idle time between each run.
Time zones¶
By default, all interpretation and scheduling is done in the machine's localtime zone (time.Local). You can specify a different time zone on construction:
cron.New( cron.WithLocation(time.UTC))
Individual cron schedules may also override the time zone they are to beinterpreted in by providing an additional space-separated field at the beginningof the cron spec, of the form "CRON_TZ=Asia/Tokyo".
For example:
# Runs at 6am in time.Localcron.New().AddFunc("0 6 * * ?", ...)# Runs at 6am in America/New_Yorknyc, _ := time.LoadLocation("America/New_York")c := cron.New(cron.WithLocation(nyc))c.AddFunc("0 6 * * ?", ...)# Runs at 6am in Asia/Tokyocron.New().AddFunc("CRON_TZ=Asia/Tokyo 0 6 * * ?", ...)# Runs at 6am in Asia/Tokyoc := cron.New(cron.WithLocation(nyc))c.SetLocation("America/New_York")c.AddFunc("CRON_TZ=Asia/Tokyo 0 6 * * ?", ...)
The prefix "TZ=(TIME ZONE)" is also supported for legacy compatibility.
Be aware that jobs scheduled during daylight-savings leap-ahead transitions willnot be run!
Job Wrappers¶
A Cron runner may be configured with a chain of job wrappers to addcross-cutting functionality to all submitted jobs. For example, they may be usedto achieve the following effects:
- Recover any panics from jobs (activated by default)
- Delay a job's execution if the previous run hasn't completed yet
- Skip a job's execution if the previous run hasn't completed yet
- Log each job's invocations
Install wrappers for all jobs added to a cron using the `cron.WithChain` option:
cron.New(cron.WithChain(cron.SkipIfStillRunning(logger),))
Install wrappers for individual jobs by explicitly wrapping them:
job = cron.NewChain(cron.SkipIfStillRunning(logger),).Then(job)
Thread safety¶
Since the Cron service runs concurrently with the calling code, some amount ofcare must be taken to ensure proper synchronization.
All cron methods are designed to be correctly synchronized as long as the callerensures that invocations have a clear happens-before ordering between them.
Logging¶
Cron defines a Logger interface that is a subset of the one defined ingithub.com/go-logr/logr. It has two logging levels (Info and Error), andparameters are key/value pairs. This makes it possible for cron logging to pluginto structured logging systems. An adapter, [Verbose]PrintfLogger, is providedto wrap the standard library *log.Logger.
For additional insight into Cron operations, verbose logging may be activatedwhich will record job runs, scheduling decisions, and added or removed jobs.Activate it with a one-off logger as follows:
cron.New(cron.WithLogger(cron.VerbosePrintfLogger(log.New(os.Stdout, "cron: ", log.LstdFlags))))
Implementation¶
Cron entries are stored in an array, sorted by their next activation time. Cronsleeps until the next job is due to be run.
Upon waking:
- it runs each entry that is active on that second
- it calculates the next run times for the jobs that were run
- it re-sorts the array of entries by next activation time.
- it goes to sleep until the soonest job.
Index¶
- type Chain
- type ConstantDelaySchedule
- type Cron
- func (c *Cron) AddFunc(spec string, cmd func()) (EntryID, error)
- func (c *Cron) AddJob(spec string, cmd Job) (EntryID, error)
- func (c *Cron) Entries() []Entry
- func (c *Cron) Entry(id EntryID) Entry
- func (c *Cron) Location() *time.Location
- func (c *Cron) Remove(id EntryID)
- func (c *Cron) Run()
- func (c *Cron) Schedule(schedule Schedule, cmd Job) EntryID
- func (c *Cron) Start()
- func (c *Cron) Stop() context.Context
- type Entry
- type EntryID
- type FuncJob
- type Job
- type JobWrapper
- type Logger
- type Option
- type ParseOption
- type Parser
- type Schedule
- type ScheduleParser
- type SpecSchedule
Constants¶
This section is empty.
Variables¶
This section is empty.
Functions¶
This section is empty.
Types¶
typeChain¶
type Chain struct {// contains filtered or unexported fields}
Chain is a sequence of JobWrappers that decorates submitted jobs withcross-cutting behaviors like logging or synchronization.
funcNewChain¶
func NewChain(c ...JobWrapper)Chain
NewChain returns a Chain consisting of the given JobWrappers.
typeConstantDelaySchedule¶
ConstantDelaySchedule represents a simple recurring duty cycle, e.g. "Every 5 minutes".It does not support jobs more frequent than once a second.
funcEvery¶
func Every(durationtime.Duration)ConstantDelaySchedule
Every returns a crontab Schedule that activates once every duration.Delays of less than a second are not supported (will round up to 1 second).Any fields less than a Second are truncated.
typeCron¶
type Cron struct {// contains filtered or unexported fields}
Cron keeps track of any number of entries, invoking the associated func asspecified by the schedule. It may be started, stopped, and the entries maybe inspected while running.
funcNew¶
New returns a new Cron job runner, modified by the given options.
Available Settings
Time Zone Description: The time zone in which schedules are interpreted Default: time.LocalParser Description: Parser converts cron spec strings into cron.Schedules. Default: Accepts this spec: https://en.wikipedia.org/wiki/CronChain Description: Wrap submitted jobs to customize behavior. Default: A chain that recovers panics and logs them to stderr.
See "cron.With*" to modify the default behavior.
func (*Cron)AddFunc¶
AddFunc adds a func to the Cron to be run on the given schedule.The spec is parsed using the time zone of this Cron instance as the default.An opaque ID is returned that can be used to later remove it.
func (*Cron)AddJob¶
AddJob adds a Job to the Cron to be run on the given schedule.The spec is parsed using the time zone of this Cron instance as the default.An opaque ID is returned that can be used to later remove it.
func (*Cron)Schedule¶
Schedule adds a Job to the Cron to be run on the given schedule.The job is wrapped with the configured Chain.
typeEntry¶
type Entry struct {// ID is the cron-assigned ID of this entry, which may be used to look up a// snapshot or remove it.IDEntryID// Schedule on which this job should be run.ScheduleSchedule// Next time the job will run, or the zero time if Cron has not been// started or this entry's schedule is unsatisfiableNexttime.Time// Prev is the last time this job was run, or the zero time if never.Prevtime.Time// WrappedJob is the thing to run when the Schedule is activated.WrappedJobJob// Job is the thing that was submitted to cron.// It is kept around so that user code that needs to get at the job later,// e.g. via Entries() can do so.JobJob}
Entry consists of a schedule and the func to execute on that schedule.
typeJobWrapper¶
JobWrapper decorates the given Job with some behavior.
funcDelayIfStillRunning¶
func DelayIfStillRunning(loggerLogger)JobWrapper
DelayIfStillRunning serializes jobs, delaying subsequent runs until theprevious one is complete. Jobs running after a delay of more than a minutehave the delay logged at Info.
funcRecover¶
func Recover(loggerLogger)JobWrapper
Recover panics in wrapped jobs and log them with the provided logger.
funcSkipIfStillRunning¶
func SkipIfStillRunning(loggerLogger)JobWrapper
SkipIfStillRunning skips an invocation of the Job if a previous invocation isstill running. It logs skips to the given logger at Info level.
typeLogger¶
type Logger interface {// Info logs routine messages about cron's operation.Info(msgstring, keysAndValues ...interface{})// Error logs an error condition.Error(errerror, msgstring, keysAndValues ...interface{})}
Logger is the interface used in this package for logging, so that any backendcan be plugged in. It is a subset of the github.com/go-logr/logr interface.
DefaultLogger is used by Cron if none is specified.
DiscardLogger can be used by callers to discard all log messages.
funcPrintfLogger¶
PrintfLogger wraps a Printf-based logger (such as the standard library "log")into an implementation of the Logger interface which logs errors only.
funcVerbosePrintfLogger¶
VerbosePrintfLogger wraps a Printf-based logger (such as the standard library"log") into an implementation of the Logger interface which logs everything.
typeOption¶
type Option func(*Cron)
Option represents a modification to the default behavior of a Cron.
funcWithChain¶
func WithChain(wrappers ...JobWrapper)Option
WithChain specifies Job wrappers to apply to all jobs added to this cron.Refer to the Chain* functions in this package for provided wrappers.
funcWithLocation¶
WithLocation overrides the timezone of the cron instance.
funcWithParser¶
func WithParser(pScheduleParser)Option
WithParser overrides the parser used for interpreting job schedules.
funcWithSeconds¶
func WithSeconds()Option
WithSeconds overrides the parser used for interpreting job schedules toinclude a seconds field as the first one.
typeParseOption¶
type ParseOptionint
Configuration options for creating a parser. Most options specify whichfields should be included, while others enable features. If a field is notincluded the parser will assume a default value. These options do not changethe order fields are parse in.
const (SecondParseOption = 1 <<iota// Seconds field, default 0SecondOptional// Optional seconds field, default 0Minute// Minutes field, default 0Hour// Hours field, default 0Dom// Day of month field, default *Month// Month field, default *Dow// Day of week field, default *DowOptional// Optional day of week field, default *Descriptor// Allow descriptors such as @monthly, @weekly, etc.)
typeParser¶
type Parser struct {// contains filtered or unexported fields}
A custom Parser that can be configured.
funcNewParser¶
func NewParser(optionsParseOption)Parser
NewParser creates a Parser with custom options.
It panics if more than one Optional is given, since it would be impossible tocorrectly infer which optional is provided or missing in general.
Examples
// Standard parser without descriptorsspecParser := NewParser(Minute | Hour | Dom | Month | Dow)sched, err := specParser.Parse("0 0 15 */3 *")// Same as above, just excludes time fieldssubsParser := NewParser(Dom | Month | Dow)sched, err := specParser.Parse("15 */3 *")// Same as above, just makes Dow optionalsubsParser := NewParser(Dom | Month | DowOptional)sched, err := specParser.Parse("15 */3")
typeSchedule¶
type Schedule interface {// Next returns the next activation time, later than the given time.// Next is invoked initially, and then each time the job is run.Next(time.Time)time.Time}
Schedule describes a job's duty cycle.
funcParseStandard¶
ParseStandard returns a new crontab schedule representing the givenstandardSpec (https://en.wikipedia.org/wiki/Cron). It requires 5 entriesrepresenting: minute, hour, day of month, month and day of week, in thatorder. It returns a descriptive error if the spec is not valid.
It accepts
- Standard crontab specs, e.g. "* * * * ?"
- Descriptors, e.g. "@midnight", "@every 1h30m"
typeScheduleParser¶added inv3.0.1
ScheduleParser is an interface for schedule spec parsers that return a Schedule
typeSpecSchedule¶
type SpecSchedule struct {Second, Minute, Hour, Dom, Month, Dowuint64// Override location for this schedule.Location *time.Location}
SpecSchedule specifies a duty cycle (to the second granularity), based on atraditional crontab specification. It is computed initially and stored as bit sets.