What is Pipeline in Jenkins

“A Bookish Definition, Pipeline is a workflow with a group of events or jobs that are chained and integrated with each other in sequence.”

Every job in a pipeline has some dependency on one or more other jobs.

Let us understand …... in an easy way!

Every pipe has Inlet and Outlet

So if this is a pipe, then what is a pipeline?

The pipeline will consist of multiple sections of a pipe and it can also have multiple Inlets and Outlets.

And

Every section will do some processing/actions and this processing/actions in our case will be done by ‘'Job’'

Let us see, how this applicable in software delivery workflow,

The continuous delivery pipeline will consist of 4 major stages.

  1. Build
  2. Deploy
  3. Test
  4. Release

And every stage has some jobs, and these jobs are integrated with each other and work in a sequence.

So we call it a Continuous Delivery Pipeline.

As mentioned above, every section has different jobs, Build section has Build Jobs, and then they will be a feedback or notification mechanism, and similarly, there will be other sections and jobs.

And when this system works together in a sequence, in an integrated way we call it Continuous Delivery Pipeline.

Now Pipeline as a concept, in Jenkins or as DevOps as a whole is mostly used with continuous delivery and deployment integration. However, Pipeline is a system where multiple sections or jobs can be integrated into a sequence and work as a workflow.

Now I think you have a basic idea of what Jenkins pipeline is.

Thanks …...

--

--

Niluka Sripali Monnankulama
Many Minds

An IT professional with over 7+ years of experience. Member of the WSO2 Identity & Access Management Team.