Pipeline

The syntax for defining a Pipeline, either in the web UI or with a Jenkinsfile is the same, but it’s kind of difficult for users who are not familiar with Jenkinsfile. To reduce the learning curve for Jenkinsfile syntax, KubeSphere provides a visual editor that allows users to simply enter a few configuration information on the web UI and it will automatically generate the pipeline and Jenkinsfile. You can also edit Jenkinsfile directly, and combine some of the plugins provided by the KubeSphere to customize complex pipelines for more complex scenarios.

A node is a machine which is part of the Jenkins environment and is capable of executing a Pipeline.

A single task. Fundamentally, a step tells Jenkins what to do at a particular point in time (or “step” in the process). For example, to execute the shell command make use the sh step: sh ‘make’. When a plugin extends the Pipeline DSL, that typically means the plugin has implemented a new step.

Create a Pipeline

It allows users to create a pipeline in two ways as following:

• Jenkinsfile out of SCM: It does not requires Jenkinsfile in your source code repository, since it supports creating a pipeline build process in the web UI. This document gives an example to walk you through the basic use of this type, see .

Reference

Jenkins Pipeline Documentation