Build Pipeline Plugin Release 1.2.2

Posted on

We are pleased to announce the availability of version 1.2.2.
The release addressed bugs.

Bug Fixes

The following defects have been resolved. Remaining defects are visible from the google code issue tracker (http://code.google.com/p/build-pipeline-plugin/issues/list).

Defect ID Summary
42 Renaming pipeline jobs breaks pipeline
47 Build Pipeline View cannot display full downstream projects
48 Downstream parameterized job picking up upstream settings

Documentation

The documentation is available from theĀ Hudson andĀ Jenkins wikis.

4 thoughts on “Build Pipeline Plugin Release 1.2.2

    Michael Schmook said:
    November 23, 2011 at 8:57 pm

    I find the Build Pipeline Plugin a great tool to setup a full deployment pipeline. Are you still working on this plugin, or has the project died?

    I noticed that a lot of people (me included) ran into the problem of not being able to pass parameters to manually triggered downstream jobs. Is there a solution for this planned?

    The manually triggered downstream jobs are a great part of the plugin, but rather useless if theres no way to retrieve informations from the particular upstream job, like the svn revision number that was used in the pipeline run.

    Bedwyr Humphreys said:
    February 15, 2012 at 2:50 am

    I get around this by writing these values to a property file which i then copy over to the downstream job using copy artifacts plugin.

    Marcos Sousa said:
    March 15, 2012 at 3:16 am

    I’m trying to use this plugin but I’m facing some trouble… I’m not seeing Build Pipeline View in the new job wizard. Is there any configuration to be made? I’m using Pipeline plugin 1.2.3 and Jenkins 1.447. Thanks

      Zachary Young said:
      March 30, 2012 at 10:23 am

      At the very least, you create a “Pipeline” view, not a job.

Leave a Reply

Your email address will not be published. Required fields are marked *