Skip to content

Added task execution to hold information for one single try #7

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

Merged
merged 3 commits into from
Feb 27, 2016

Conversation

wachterjohannes
Copy link
Member

No description provided.

@wachterjohannes
Copy link
Member Author

@alexander-schranz @chirimoya would that be enough for your project? i would like to release that in this way.

For a future release i will refactor maybe the task to combine frequent task and use the executions to hold informations for each run and hold the "frequency" in form of a cron-expression in the task itself. this frequency would be null if it will be executed only once. the start and end date would that used as:

  • not execute before (start-date)
  • not execute after (end-date)

which would be a better solution than the current one.

@alexander-schranz
Copy link
Member

cant imagine how it is implemented in the entity. if i look at the tasks table see there task_key, started, finished its ok.

@wachterjohannes wachterjohannes merged commit d67e290 into master Feb 27, 2016
@wachterjohannes wachterjohannes deleted the feature/task-timing branch February 27, 2016 11:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants