Create a null job type for all hosts, to allow for "prerun only" jobs
Sometimes it is useful to separate preruns from the jobs that require them, either to apply the same preruns to multiple jobs without rerunning them, or to simplify restarts, where some preruns, but not all, should be skipped. It also allows "file watcher" type preruns to begin execution before the dependent job is eligible.
In some cases, the preruns can be defined as standalone jobs, but they are handled differently than true preruns, especially with regard to failure and history, and in some cases, there is no "primary command" for the prerun actions, so the current solution is to create a job with a dummy program or command and attach the preruns to it. A true null job type would be more efficient and less error prone.
Comments: 1
-
02 May, '22
YannAnd yet, the "deactivation" of a job in "dummy" and its reactivation without loss of data is a huge MISS in opcon. I don't understand the "declined", unless there is another possibility?
Coding with null jobs requires the creation of an extra chain and a waste of time.