Replies: 3 comments
|
Use dependencies. Make one job that creates a batch of jobs and one followup job that depends on all the batch jobs. The followup job can then check if more batches are needed. |
0 replies
|
I'm trying with
however, even with this simple example I hit a problem: how to limit the |
0 replies
|
I'm using that approach in Cavil: https://github.com/openSUSE/cavil/blob/a527755a49ccd3feaa0cdca14227bf3901c99f8e/lib/Cavil/Task/Index.pm#L55 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'd like to enqueu a task that will perform a "batch" of operations, and then exit. But then I need to execute another batch unless the all work is done (this is data retrieval task).
So my idea would be to enqueue again the same task (or reschedule for execution) until all it's done.
But what is the best way to do this?
I was wondering to do something like:
but I don't think this will trigger a new execution. Otherwise, is there a way to re-perform (or re-run) an already compelted job as a new one?
All reactions