Build Pipeline Plugin

Skip to end of metadata
Go to start of metadata

Summary 

This plugin provides a Build Pipeline View of upstream and downstream connected jobs that typically form a build pipeline.  In addition, it offers the ability to define manual triggers for jobs that require intervention prior to execution, e.g. an approval process outside of Jenkins.

Plugin Information

Plugin ID build-pipeline-plugin Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
Dependencies
1.4.2
Nov 03, 2013
1.521
dashboard-view (version:2.2, optional)
jquery (version:1.7.2-1)
parameterized-trigger (version:2.17)
Source Code
Issue Tracking
Maintainer(s)
GitHub
Open Issues
Centrum Systems (id: centrum)
Usage Installations 2013-Apr 5546
2013-May 5838
2013-Jun 6085
2013-Jul 6420
2013-Aug 6589
2013-Sep 6939
2013-Oct 7434
2013-Nov 7709
2013-Dec 7682
2014-Jan 8208
2014-Feb 8619
2014-Mar 9185
How to Contribute
Lets make this better together! Build Pipeline Plugin - How to Contribute

Release Notes

1.3.3
1.3.1
1.3.0 - Also see the roadmap for details.
1.2.4 - Also see the roadmap for details.
1.2.2
1.2.1
1.2
1.1.2
1.1.1
1.0.0

Overview

Continuous Integration has become a widely adopted practice in modern software development. Jenkins & Hudson are great tools for supporting Continuous Integration.

Taking it to the next level: Continuous integration can become the centerpiece of your deployment pipeline, orchestrating the promotion of a version of software through quality gates and into production. By extending the concepts of CI you can create a chain of jobs each one subjecting your build to quality assurance steps. These QA steps may be a combination of manual and automated steps. Once a build has passed all these, it can be automatically deployed into production.

In order to better support this process, we have developed the Build Pipeline Plugin. This gives the ability to form a chain of jobs based on their upstream\downstream dependencies. Downstream jobs may, as per the default behaviours, be triggered automatically ,or by a suitable authorised user manually triggering it.

You can also see a history of pipelines in a view, the current status and where each version got to in the chain based on its revision number in VCS.

Screenshots

The Pipeline View

Configuration

View Configuration

  1. Install the plugin using the Hudson\Jenkins Plugin Manager and restart.
  2. Create a view of the new type Build Pipeline View.
    You will then be redirected directly to the configuration page.
  3. The table below outlines what each interesting parameter controls:
    Name The name of the Build Pipeline View
    Description This message will be displayed on the view page. Useful for describing what this view is about, or linking to relevant resources. Can contain HTML tags.
    Build Pipeline View Title Gives a title to the page that displays the view
    Select Initial Job This is the first job in the build pipeline. It will traverse through the downstream jobs to build up the entire build pipeline.
    Select from a drop-down list of jobs.
    No of Displayed Builds The number of historical builds to be displayed on a page.
    Restrict triggers to most recent successful builds Select this option to restrict the display of a Trigger button to only the most recent successful build pipelines.
    Yes: Only the most recent successful builds displayed on the view will have a manual trigger button for the next build in the pipeline.
    No: All successful builds displayed on the view will have a manual trigger button for the next build in the pipeline.
    Always allow manual trigger on pipeline steps Select this option if you want to manually execute or re-execute any step of the pipeline at any time.
    Show pipeline parameters Select this option if you want to display the parameters used to run the first job in the pipeline.

Job Configuration

  1. Navigate to the Job configuration page.
  2. Scroll down to the Post-build Actions section.
    1. For an Automated downstream build step;
      To add a build step that will trigger automatically upon the successful completion of the previous one:
      1. Select the Build other projects check-box
      2. Enter the name(s) of the downstream projects in the Projects to build field. (n.b. Multiple projects can be specified by using comma, like "abc, def".)
    2. For a Manually Triggered downstream build step:
      To add a build step that will wait for a manual trigger:
      1. Select the Build Pipeline Plugin -> Manually Execute Downstream Project check-box
      2. Enter the name(s) of the downstream projects in the Downstream Project Names field. (n.b. Multiple projects can be specified by using comma, like "abc, def".)
  3. Click Save
Automatic & Manual downstream build steps
The Build Pipeline Plugin handles the creation of multiple automatic and/or manually triggered downstream build steps on the same project.

Upgrading from Release 1.0.0

When upgrading from 1.0.0 to 1.1.x some of the previous view and job configuration fields have been removed. You may notice some errors of the following errors appearing in the Hudson/Jenkins log.

WARNING: Skipping a non-existent field downstreamProjectName
com.thoughtworks.xstream.converters.reflection.NonExistentFieldException: No such field
au.com.centrumsystems.hudson.plugin.buildpipeline.trigger.BuildPipelineTrigger.downstreamProjectName

This is because the configuration files refer to old fields that may no longer exist.
In order to correct these issues go to the Job configuration page, confirm that all of the details are correct and click on the Save button.

More on Pipelines

The canonical reference for pipelines is the book Continuous Delivery.

Chapter 5 of the book, which describes how deployment pipelines work, is available for free here.

Labels

Edit
plugin-builder plugin-builder Delete
plugin-post-build plugin-post-build Delete
plugin-ui plugin-ui Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Add Comment