The document discusses implementing a CI/CD pipeline using Jenkins and its plugin architecture, specifically highlighting the use of the 'build pipeline plugin'. It details the configuration of jobs for build, deploy, and test, demonstrating both automatic and manual triggers within the pipeline structure. The conclusion emphasizes Jenkins' extensive plugin availability, customization options, and its suitability as an open-source solution for continuous delivery pipelines.

1. Jenkins
http://jenkins-ci.org/
www.vishalbiyani.com

2. With Jenkin’s
plugin based
architecture- we
need plugins for
building pipelines
www.vishalbiyani.com
We found two and
we used “Build
pipeline plugin” for
demonstrating the
concept

3. A sample pipeline
from the plugin
page
www.vishalbiyani.com

4. BuildPipeline is
available as a view
in Jenkins – so
let’s add that
www.vishalbiyani.com
And let’s configure
one test job. The
job has
configurations to
attach it to a build
pipeline

5. As a result of
above steps- we
get a very basic
pipeline – now let’s
add some real
material to it
www.vishalbiyani.com

6. 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
www.vishalbiyani.com

7. 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
www.vishalbiyani.com

8. 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
manuallysubsequent jobs
are auto triggered
www.vishalbiyani.com

9. 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!
www.vishalbiyani.com

10. A history of
pipeline
www.vishalbiyani.com

11. 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
www.vishalbiyani.com