Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

Summary

This plugin creates a pipeline of Hudson\Jenkins jobs and gives a view so that you can visualise it.

Plugin Information

View Build Pipeline on the plugin site for more information.

The current version of this plugin may not be safe to use. Please review the following warnings before use:

New version to be released

We recently made Build Pipeline Plugin 1.3.0 APLHA available. We would appreciate if you could help us test it. We'll be looking to release it properly to Jenkins in the following days.

How to Contribute

Lets make this better together! Build Pipeline Plugin - How to Contribute

Roadmap

Have a look at what is coming up and contribute your suggestions - Build Pipeline Plugin - Roadmap

Release Notes

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 it's revision number in VCS.

Feedback

We'd love to hear about your experience using it or any enhancement suggestions - please let us know:

  • Email: build-pipeline@centrumsystems.com.au (mailto: build-pipeline@centrumsystems.com.au)
  • Twitter:
    twitter.com

Screenshots

The Pipeline View

Configure View

Navigate to the configure view page.

Start Build of Pipeline for ...

Invokes a new build of the initial job in the build pipeline.

View/Hide Build Pipeline Icon Legend

Toggles the view of the Build Pipeline Icon legend.

Pipeline Legend

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 Trigger to the Most Recent Build

    Where applicable, restricts the appearance of a Trigger button to only the most recent build pipeline.
    Yes: Only the latest build pipeline will have a manual trigger button.
    No: All builds displayed on the view will have a manual trigger button.

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.

Source Code

Hosted on Google Code

This is hosted on Google Code so that we can support both Jenkins and Hudson.

Please use Google Code rather than this page to ask questions, report bugs and request features.

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.

Commercial Support

Are you facing these challenges as you try to meet your delivery commitments?

  • It takes a long time for projects or new development resources to become productive.
  • Inability to scale resources or development partners to meet business demands.
  • Inconsistent quality of software deliverables across project teams or suppliers.
  • Error prone manual build processes which are difficult to scale
  • Inconsistent application of tools and processes resulting in key resource dependencies.
  • Dependency on hero factor in software deployments – asking too much of individuals to successfully implement software.
  • Uncertainty around the impact of change
  • Lack of visibility of the quality or status of change until late in the delivery lifecycle.
  • Spiralling costs of change due to ever increasing technical debt

Centrum Systems have developed an offering we call Software Delivery Mastery (SDM). We can help in the following areas:

  • Software build process
  • Continuous integration
  • Deployment automation
  • Automated inspection and testing
  • Environment provisioning and configuration management
  • Project inception / developer on-boarding.

For information about how we can help you please contact us or visit http://www.centrumsystems.com.au

  • No labels