A pipeline is a collection of jobs that brings the product from version control under the control of the end clients by utilizing computerization apparatuses. It is an element used to consolidate consistent conveyance in our product advancement work process. Throughout the years, there have been various Jenkins pipeline releases including, Jenkins Build stream, Jenkins Build Pipeline module, Jenkins Workflow, and so forth. What are the key highlights of these modules? They speak to different Jenkins jobs as one entire work process as a pipeline. These pipelines are an accumulation of Jenkins employments which trigger each other in a predefined arrangement.

Let me clarify this with a model. ASSUME I'm building up a little application on Jenkins and I need to fabricate, test and convey it. To do this, I will distribute 3 employment to play out each procedure. Along these lines, job1 would be for fabricating, job2 would perform tests and job3 for an organization. I can utilize the Jenkins assemble pipeline module to play out this assignment. In the wake of making three employments and binding them in a grouping, the fabricate module will RUN these occupations as a pipeline.

Step 1:  For creating a build pipeline, First CREATE a set of jobs.

Step 2:  Now create a build pipeline view and in the configure section add the first job that you want to run in the pipeline

Step 3: Now for every job, add a post-build ACTION, which can be modified many ways, for example, manual trigger or automatic trigger on the success of the build.

step 4: Once all the downstream jobs are configured, just build the P1 job. and go to the new pipeline view that you have created.

Note: You won't see a pipeline until the first job is started. In this example, after the p1 job is started you will start seeing a pipeline.