Job scheduling
This function only supports saturn 3.3.0 and above
1 Overview
Sometimes due to business needs, we need to schedule jobs in a workflow manner:
JobA dispatch after dispatch successfully Jobb , Jobb dispatch schedule after the success of JobC
Saturn provides this ability, which we call job scheduling. Job scheduling forms a directed acyclic graph of jobs, which are called sequentially in the order of the graph.
2 Concept
In a call link, there are concepts of upstream and downstream. Taking the above example as an example, JobA is the most upstream of this call link or called root, and JobB and JobC are downstream of root.
The most upstream job (root job) can be a Java timing job or a Shell timing job.
The job type of the downstream job is called 被动作业. Passive job can be subdivided into Java被动作业and Shell被动作业.
In version 3.3.0, the number of fragments of jobs in the entire call chain can only be 1, and the link must not form a ring.
3 Access steps
3.1 Development work
All jobs in the job scheduling (whether root or passive) must be Java timing jobs or Shell timing jobs. For the development of Java timing jobs and Shell timing jobs, please see the corresponding chapters, and I won’t repeat them here.
3.2 Define the job calling sequence in the Console
3.2.1 Define Root Job
Root job is a Java timing job or Shell timing job. For details, see Java作业the Console Creation Job chapter.
3.2.2 Define downstream operations (passive operations)
Select "Java Passive Job" or "Shell Passive Job" for job type, and select Root job or other passive jobs for upstream job.
3.2.3 View call dependencies
On the domain job overview page, click 作业依赖图to see the calling sequence of job scheduling for the entire domain.
