Posted on

Following great community feedback about the Build Pipeline Plugin 1.1.1, we are pleased to announce the availability of version 1.1.2. ย The release addressed a few bugs and expanded its SCM support (namely Git and Mercurial).


The following defects have been resolved. Remaining defects are visible from the google code issue tracker (

Defect ID Summary
2 Support Git SHA1 for “revision”
16 Add date/time of execution
19 Build view empty, NPE in the log
22 Support for mercurial revision number
27 Build Pipeline and Copy Artifact plugin combination causes NPE

Build Pipeline Plugin


    Jaakko Aro said:
    May 4, 2011 at 4:09 am


    Thanks for the great plugin, it seems to be very well done.. I work in a project which is probably one of the largest Jenkins “installations” ever, we have around 3000 jobs on one Jenkins instance and it’s working ok with it.

    The biggest problem with it is that there’s a lot of projects coming and going and i really need a regular expression support to specify the downstream. And actually i have already started to create it, but lets see when i have enough time to finish it.. I haven’t decided how i’m going to implement the final solution, but I prefer implementing it in a way that you guys would take it as a part of the actual build pipeline plugin.. So if you prefer some certain way of doing it, i’m open to ideas:)

      Marcin Popielarz said:
      May 11, 2011 at 9:20 pm

      Hi Jaakko,

      We are glad that you are enjoying the plugin. Did you already have some sample code to define dependencies using a regex?

        Jaakko Aro said:
        May 28, 2011 at 8:52 pm


        The regex -stuff works already, but i still need to implement all the necessary stuff so that it handles situations like project renaming etc. correctly. Most of the functionality is already implemented, so it shouldn’t take so long, but it depends when I got time to finish it.. Also the tests have to be refactored ๐Ÿ™‚

          Geoff Bullen said:
          June 1, 2011 at 2:44 pm

          Looking forward to it!

    Paul Marshall said:
    May 18, 2011 at 6:18 pm

    Just downloaded 1.1.2 of Build Pipeline PlugIn for Hudson.
    Looks great, thanks.
    1) How is the “revision” populated (grey box against each pipeline)?
    2) With a long pipeline, not all the stages can fit on one page when shown on an “information radiator”. The content of each stage instance could be configurable i.e the default is to show the job name, build number and duration, but I may only want to show the build number, thus reducing the size of the block.

    Let me know….

      Geoff Bullen said:
      June 1, 2011 at 2:44 pm

      1) The revision number is retrieved using the remote access API at the moment as there is no easy way to get at it from the core. Because of this, the anonymous user needs to be granted read access
      2) Interesting idea, perhaps you could raise an enhancement request – . Or, better still, submit a patch!

Leave a Reply

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