How to Do Release Process in Continuous Delivery Using Jenkins

Summary

Visualisation of Continuous Delivery pipelines. Renders pipelines based on upstream/downstream jobs or Jenkins pipelines. Provides a full screen view for information radiators.
In Continuous Delivery, feedback and visualisation of the delivery process is one of the most important aspects. When using Jenkins as a build/CI/CD server, it is with the Delivery Pipeline plugin possible to visualise one or more delivery pipelines in the same view, even in full screen.

{height="250"}

Jenkins jobs are tagged with a stage and a task name. In the screenshot above, the pipeline consists of three stages called Commit stage, Test stage and Deployment. The first stage consists of two tasks called "Build, package and run unit tests" and "Build and publish artifacts". Each task corresponds to a traditional Jenkins job.

The plugin requires your pipelines to be built using traditional Jenkins jobs with downstream/upstream relationships or using Jenkins pipelines. For downstream/upstream jobs, automatic promotion steps use the Parameterized Trigger Plugin while manual steps are provided using the Build Pipeline plugin manual trigger (see example with manual trigger below). Aggregated view shows the latest version for each stage.

{height="250"}

Full screen view

Example screenshot when using the Delivery Pipeline plugin in full screen view (suitable for information radiators):

{height="250"}

Configuration

Using traditional Jenkins jobs

• Create jobs with downstream/upstream relationships.
• Tag your Jenkins jobs with which stage it belongs to and the task name in the "Delivery Pipeline configuration" section.

Jenkins pipelines

• Create a Jenkins pipeline. No additional configuration is needed as the stage nodes are used for rendering the pipeline view. Tasks can be defined using the task pipeline step. Multi-branch pipelines are also supported.
• The following blog post shows how to use task's inside pipeline stages for a more fine-grained visualization of pipelines using the Delivery Pipeline plugin: http://blog.diabol.se/?p=1021

View

Manual Triggers

• Make sure that the Build Pipeline plugin is installed and enabled.
• Create or edit a job and add a Postbuild action
  

Known issues

JUnit plugin needs to be installed and enabled.
If arrows are missing between the stages, please take look at JENKINS-28055

Need help

Join our Google Group https://groups.google.com/forum/\#\\!forum/delivery-pipeline-plugin\\\|https://groups.google.com/forum/\#\\!forum/delivery-pipeline-plugin (https://groups.google.com/forum/\#\\!forum/delivery-pipeline-plugin)

Open Tickets (bugs and feature requests)

type

key

summary

assignee

reporter

priority

status

resolution

created

updated

due

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

Changelog

Starting from version 0.10.1, the Delivery Pipeline Plugin is released completely automatically and the generated release notes can be found on GitHub:

https://github.com/Diabol/delivery-pipeline-plugin/releases/

0.10.0 (Nov 16 2016)

https://github.com/Diabol/delivery-pipeline-plugin/releases/tag/delivery-pipeline-plugin-0.10.0

0.9.12 (Jun 8 2016)

https://github.com/Diabol/delivery-pipeline-plugin/releases/tag/delivery-pipeline-plugin-0.9.12

0.9.11 (May 24 2016)

• Added missing icons from contrast theme JENKINS-35086 PR

0.9.10 (May 20 2016)

0.9.9 (Mar 28 2016)

0.9.8 (Dec 12 2015)

0.9.7 (Aug 27 2015)

• Delivery pipeline sometimes uses job name instead of taskname JENKINS-30170 PR PR

0.9.6 (Aug 26 2015)

Release 0.9.5 (Jul 28 2015)

Release 0.9.4 (09 Jun 2015)

Release 0.9.3 (02 May 2015)

• MethodNotAllowed error when start new build JENKINS-28582 PR

Release 0.9.2 (01 May 2015)

Release 0.9.1 (17 May 2015)

Release 0.9.0 (15 May 2015)

Release 0.8.11 (23 March 2015)

Release 0.8.10 (17 March 2015)

Release 0.8.9 (04 February 2015)

Release 0.8.8 (10 December 2014)

Release 0.8.7 (16 November 2014)

Release 0.8.6 (26 August 2014)

Release 0.8.5 (17 August 2014)

Release 0.8.4 (07 August 2014)

• Stage connector arrows missing in version 0.8.2 JENKINS-23824

Release 0.8.3 (03 August 2014)

• Use getRootUrl instead of getRootUrlFromRequest JENKINS-24019

Release 0.8.2 (02 July 2014)

Release 0.8.1 (16 June 2014)

Release 0.8.0 (14 May 2014)

• Allow manual trigger JENKINS-21009

Release 0.7.5 (03 May 2014)

Release 0.7.4 (14 April 2014)

Release 0.7.3 (03 April 2014)

• Pipelines are mixed up when same stage/step names are used JENKINS-22423

Release 0.7.2 (17 March 2014)

• Parallel stages display distorted JENKINS-22211

Release 0.7.1 (15 March 2014)

• Delivery Pipeline View only shows first component JENKINS-22189

Release 0.7.0 (10 March 2014)

Release 0.6.10 (30 January 2014)

Release 0.6.9 (20 January 2014)

• Add pipelines dynamically with regular expressions JENKINS-20717

Release 0.6.8 (07 January 2014)

Release 0.6.7 (22 November 2013)

• Triggered by includes culprits JENKINS-20721

Release 0.6.6 (20 November 2013)

• Consider "Trigger/call builds on other projects" JENKINS-20588

Release 0.6.5 (14 November 2013)

Release 0.6.4 (06 November 2013)

• Backport code to run on Java 1.6 JENKINS-20441

Release 0.6.3 (04 November 2013):

• Configurable update interval JENKINS-20388

Release 0.6.2 (18 October 2013):

Release 0.6.1 (08 October 2013)

• First public release

gouldforepland1950.blogspot.com

Source: https://plugins.jenkins.io/delivery-pipeline-plugin/

Share this post