Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use standard cron syntax for --schedule #30

Merged
merged 3 commits into from
Jun 19, 2018
Merged

Conversation

SpComb
Copy link
Contributor

@SpComb SpComb commented Jun 19, 2018

Fixes #29

The --schedule option now accepts standard five-field crontab syntax, forcing seconds to 0.

The previous six-field syntax with leading seconds will now be rejected.

@SpComb SpComb added the enhancement New feature or request label Jun 19, 2018
@SpComb
Copy link
Contributor Author

SpComb commented Jun 19, 2018

Fails with the old syntax:

2018/06/19 13:26:06 Invalid --schedule=0 * * * * *: Expected exactly 5 fields, found 6: 0 * * * * *

Works with the standard syntax:

2018/06/19 16:21:42 Using --schedule="30 6 * * *", first upgrade at: 2018-06-20 06:30:00 +0300 EEST (in 14h8m17.998512199s)

@SpComb SpComb merged commit fa4625d into master Jun 19, 2018
@SpComb SpComb deleted the fix/schedule-standard-cron branch June 19, 2018 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants