3 ms·
Is it possible to start a task inside a job and have it's dependencies start up after it finishes without starting the whole job? Like, say I have a sequence o
by DannoHung 17y ago
Is it possible to start a task inside a job and have it's dependencies start up after it finishes without starting the whole job? Like, say I have a sequence of operations to one, in the middle, something screws up (like a network connection is down for some reason). Can I rerun from the step that screwed up and get the rest to follow through?
- deleted 17y ago[deleted]
- darrellsilver 17y agoIf I understand the question the answer is yes. I think you're asking if you can retry portions of a job, like if a task breaks but doesn't exit with an error, thus causing the rest of the job to continue. In this case, yes, you can retry a task in the middle of a tree of tasks, and retry all the children tasks as well. This will leave some tasks untouched (the parents and peers) and retry the children in the same order as the first time. If a task in the middle of the tree fails children tasks will not run until it's been skipped or successfully run. Retrying children tasks would be a great job for a GUI for Norc because then you could choose which children tasks to retry interactively from a web app or somesuch...
- DannoHung 17y agoYep. That's what I wanted to know. Sorry for the poor phrasing. I was little confused because it seemed like norc would only start jobs at the top level.
- darrellsilver 17y agoYeah, the terminology isn't well-defined. Jobs start with any tasks that return True when asked due_to_run(), which can be schedule, parents' status, etc. Glad I could clear it up!
- silentbicycle 17y agoProvided the events are run locally (not distributed over multiple servers), this could be done pretty easily by running make targets out of cron.