I have a requirement which expects to define dependencies over batch jobs and execute them in sequence. Briefly, job B should be executed just after job A is completed and job C should be executed just after job B is completed.
As far as I see, Nomad does not natively support defining dependency in job level. So, I am trying to find a workaround.
A possible solution can be periodically checking Nomad if a batch job has gone dead and registering the consecutive batch job if so in a third long running job. But I’m not sure if this solution will be optimal enough.
I’d like to get your opinions for better/alternative solutions.