The job the pipeline starts with. For a chained job, every job downstream of it becomes a task, grouped into stages by the Delivery Pipeline configuration of each job, and a Pipeline job the chain triggers is followed into its runs. For a Pipeline (Jenkinsfile) job, each run is a pipeline instance and each top-level stage a stage; stages nested in a stage and parallel branches become its tasks, and the runs it starts with the build step, or by triggering other jobs, follow as further stages. A multibranch project or a folder gives one pipeline per job inside it, named after the component and the job (the branch, for a multibranch project), the primary branch first.

Type the name and pick from the suggestions: a name relative to the view's folder, such as 0/build, the full name, such as Images/0/build, which is how Job DSL writes it, or a path from the top with a leading slash. The name is kept as it is typed.