{"id":40574,"date":"2016-09-21T23:07:04","date_gmt":"2016-09-21T17:37:04","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=40574"},"modified":"2024-01-02T17:44:34","modified_gmt":"2024-01-02T12:14:34","slug":"continuous-delivery-pipeline-jenkins-delivery-pipeline-view-plugin","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/continuous-delivery-pipeline-jenkins-delivery-pipeline-view-plugin\/","title":{"rendered":"Setting up Continuous-Delivery Pipeline using Jenkins\u2019 Delivery-Pipeline-View Plugin"},"content":{"rendered":"

Jenkins is a widely used CI tool which helps DevOps teams<\/a> in automating the multiple tasks. The use of Jenkins has widely increased over a period of time due to a rich set of functionalities which it provides in the form of plugins. Jenkins has plugins for automating almost everything at the infrastructure level. In this blog, I am going to explain the use of \u201cDelivery Pipeline View\u201d plugin of Jenkins by which we can setup complete continuous delivery pipeline<\/a>.<\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0\"Image
\n<\/strong><\/strong><\/p>\n

Continuous-Delivery <\/b>is the process of automating the code delivery tasks from development to production environment consisting of version control management, deployment on each environment followed by automated testing and taking decisions based on the results of the previous step. If the test cases are passed, the code will be automatically moved to the subsequent environment without any manual intervention till its deployed on production environment followed by post-deployment tasks.<\/span><\/p>\n

In Jenkins, each job has a post-build step in which we can specify the downstream projects on the basis of the result of the current step. I\u2019ve made a following flow of the build pipeline for demonstration purpose:
\n1. Dev-Deployment<\/strong>
\n2. Dev-Testing<\/strong>
\n3. UAT-Deployment<\/strong>
\n4. UAT-Testing<\/strong>
\n5. Prod-Deployment<\/strong>
\n6. Prod-Testing<\/strong><\/p>\n

Note: <\/b>Each step is an independent Jenkins job in itself. If at a\u00a0certain point, any of my steps fails, the pipeline will get stopped. Each step will be started only if the previous step has run successfully.<\/p>\n

Deplo<\/strong>yment Scenario
\n<\/b>In deployment case, I will be deploying an index page on Nginx from the git branch of the same environment of my git repository. For, e.g.,\u00a0for dev.example.com, I will be deploying the index page from the dev branch of my git repository. It contains the text that \u201cThis is dev site.\u201d<\/p>\n

Testing Scenario
\n<\/b>In my testing scenario, I am just checking whether the deployed index page contains the environment name. For e.g., \u201cThis is dev site\u201d contains the word \u201cdev\u201d in it. Means the test case is passed. The same process is repeated for all the environments.You can define the test cases as per the requirements.<\/p>\n

Also, in each job, I\u2019ve specified what are the upstream and downstream projects to build for the specific job. For eg. dev-testing has a downstream project for uat-deployment and upstream project for dev-deployment. Each downstream project will be run if its upstream project has run successfully. The below snapshot is the configuration of dev-deployment job:
\n\"dev-depl\"Image1: Post build action for downstream project<\/em><\/p>\n

\"dev-testing\"<\/p>\n

Image2:\u00a0<\/em>Upstream and downstream project for dev-testing<\/em><\/span><\/p>\n

For the view of the delivery pipeline, the required plugin is Delivery Pipeline Plugin.\u00a0<\/b>Please make sure the plugin is installed:\"plugin\"<\/strong>Image3: Installed Plugin of Delivery Pipeline View<\/em><\/p>\n

Below is my pipeline configuration:
\n<\/strong>In the pipeline configuration, we can define the endpoint jobs of the pipeline like in my case the initial job is dev-deployment and final job is prod-testing:\"pipeline-config\"<\/strong>Image4: Pipeline configuration<\/em><\/p>\n

Before Executing the Pipeline: <\/b>The status of my 3 sites (dev.example.com, uat.example.com, example.com) is as follows:\"before-dep\"<\/strong><\/strong>Image5: The status of the sites<\/em><\/p>\n

Executing the Pipeline: <\/b>Click on the build icon to start building the pipeline process:\u00a0\"pipe1\"<\/strong><\/strong>Image6: Building the pipeline<\/em><\/p>\n

Note: <\/b>If something gets break during the\u00a0pipeline, the build pipeline gets aborted. For eg. in Image7, my build 9 is aborted at dev-testing due to failure of the test cases:\"pipeview1\"<\/strong><\/strong>Image7: Failure of\u00a0pipeline<\/em><\/p>\n

After executing build-pipeline successfully:<\/b>\"deployment\"<\/strong><\/p>\n

The code has been successfully deployed on all the environments after proper testing.
\nSo, Jenkins is a fantastic tool to automate all the DevOps process. <\/strong>In my next, blog I\u2019ll be demonstrating about some other Jenkins\u00a0plugins for automation.<\/p>\n","protected":false},"excerpt":{"rendered":"

Jenkins is a widely used CI tool which helps DevOps teams in automating the multiple tasks. The use of Jenkins has widely increased over a period of time due to a rich set of functionalities which it provides in the form of plugins. Jenkins has plugins for automating almost everything at the infrastructure level. In […]<\/p>\n","protected":false},"author":170,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":20},"categories":[1174,2348,1],"tags":[4019,4017,4016,3270,2845,4015,4020,1682,4014,4018],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/40574"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/170"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=40574"}],"version-history":[{"count":1,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/40574\/revisions"}],"predecessor-version":[{"id":59832,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/40574\/revisions\/59832"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=40574"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=40574"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=40574"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}