Lines provide custom process choreography tools, research the production process in the different phases and tasks in series or parallel together, through the build, test, deployment, artificial control multi-source componentization ability, such as adopting agile iterative way to realize the process of continuous integration and delivery, feedback, finished products, research and development, operating information asymmetry between the gap, Mobilize collaboration between departments to seamlessly improve overall productivity efficiency and serve the entire software life cycle.

Overall structure drawing

Build pipelining at the front end

Determine pipeline structure

Each construction is a stage, and the following job is the child node of stage, just as the devil is born of his mother, and people are born of his mother, so every child node has a parent node.

TemplateCode: [{"stage_name": 'build ', // Name of each stage "topflag": true, // Control stage edit switch "steps": [{"auto_run": "Jobs ": [{"job_name": 'Java build ', // Name of each subtask "step_type_content": 'Java - build', / / to the user see steps category "job_content" : {compiler_id: 1, / / compile id/content/child node},}}}]]]Copy the code

Our div level structure is

<div class="father"> // nodes can be serialized and parallel <span>{stage_name} </span> // the name of each stage <div class="son"> {job_name} // each job under stage </div> </div>Copy the code

Connections between nodes

//  html
<div class="pipeline_flow_splitline"></div>、
//  css
.pipeline_flow_splitline:after {
	content: "";
	height: 100%;
	border-left: 1px solid #d9d9d9;
	position: absolute;
}
Copy the code

This completes parallelism and serialization between nodes

Now we need to bind our node to the tasks it should perform

Then bind the task to our job_content and we can run our pipeline