Using CI for continuous delivery Part 4

Jenkins

http://jenkins-ci.org/

www.vishalbiyani.com


With Jenkin’splugin based

architecture- we need plugins for building pipelines

We found two and we used “Build

pipeline plugin” for demonstrating the

concept


A sample pipeline from the plugin

page


BuildPipeline is available as a view

in Jenkins – so let’s add that

And let’s configure one test job. The

job has configurations to attach it to a build

pipeline


As a result of above steps- we get a very basic

pipeline – now let’s add some real material to it


Each individual unit of work will be a job in Jenkins. So we have build-deploy-test jobs

for Dev and QA

How to connect them to form a pipeline we

will see next


Post build actions -If we want next job to be

triggered automatically (Above) and if the next job will be kicked off

manually (Below) but is part of pipeline


We have Build, Deploy and Test for Dev

triggered automatically one

after another

But QA Deploy has a manual “Click” needed. So we can configure the way we want it. They are part of same “pipeline”

And we kicked off the QA Deploy

manually-subsequent jobs are auto triggered


One caution though: If you trigger jobs from job page and not from pipeline view – that won’t be recorded by

pipeline

I triggered #3 through pipeline then 4,5 through

job page and next run (#7) through pipeline view.

Pipeline view only cares for what it manages!


A history of pipeline

Jenkins - Concluding thoughts

• Basic support for CD pipelines

• Very high number of plugins available and heavy customizations

• The semantic was still CI oriented

• Still a very good open source option

• Can be heavily customized to achieve what is needed for a CD pipeline


Technology

Using CI for continuous delivery Part 4