Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-18464

Build Pipeline and Join plugin do not play nicely together

      I use Join Plugin to start some parallel jobs and then to execute another job when those parallel finish. When I put all of them into Build Pipeline I get the attached picture.

      It seems to me more correct to show only one box in the last column. That job named "Finish" will always be executed not more than once. These three boxes are confusing.

          [JENKINS-18464] Build Pipeline and Join plugin do not play nicely together

          please add support for this

          Michael Hüttermann added a comment - please add support for this

          Tony Sandin added a comment -

          Any news on a fix for this issue?

          Tony Sandin added a comment - Any news on a fix for this issue?

          Michael Weinrich added a comment - - edited

          I would like to help fixing this issue, but I'm totally new to Jenkins development (yet I used it for quite some time now). I tried to write a unit test to illustrate the problem (see https://github.com/InterNations/build-pipeline-plugin/compare/join-trigger-fix), however I'm stuck there. Is there anything I can do to accelerate the fix for this issue? I might even get some bounty for the fix (of course not for me but for the one fixing it ) If anyone is interested, I would ask for details on that.

          Michael Weinrich added a comment - - edited I would like to help fixing this issue, but I'm totally new to Jenkins development (yet I used it for quite some time now). I tried to write a unit test to illustrate the problem (see https://github.com/InterNations/build-pipeline-plugin/compare/join-trigger-fix ), however I'm stuck there. Is there anything I can do to accelerate the fix for this issue? I might even get some bounty for the fix (of course not for me but for the one fixing it ) If anyone is interested, I would ask for details on that.

          I also would like to help solving this issue. It seems that some work were already done here in the past: https://code.google.com/p/build-pipeline-plugin/issues/detail?id=21

          Gonzague Reydet added a comment - I also would like to help solving this issue. It seems that some work were already done here in the past: https://code.google.com/p/build-pipeline-plugin/issues/detail?id=21

          John McGehee added a comment - - edited

          WORKAROUND: Use the Multijob Plugin alone without the Build Pipeline Plugin.

          The Multijob Plugin gives you the functionality of the Join Plugin, and its configuration is more straightforward. I actually like how it displays my running build better than the Build Pipeline Plugin.

          John McGehee added a comment - - edited WORKAROUND: Use the Multijob Plugin alone without the Build Pipeline Plugin. The Multijob Plugin gives you the functionality of the Join Plugin, and its configuration is more straightforward. I actually like how it displays my running build better than the Build Pipeline Plugin.

          ickersep added a comment - https://code.google.com/p/build-pipeline-plugin/issues/detail?id=21 describes the same problem. Comment #19 ( https://code.google.com/p/build-pipeline-plugin/issues/detail?id=21#c19 ) has a fix ( https://code.google.com/r/jessica-join-support-build-pipeline-plugin/source/detail?r=b15a06a07a24adfc35638c7dd4a93dbd16f52bf6 ), but it looks it never got integrated.

          Eric Moreau added a comment -

          Is there an update on this issue?

          Eric Moreau added a comment - Is there an update on this issue?

          John McGehee added a comment - - edited

          At the Jenkins World conference over the past two days, I saw the community moving to the new Pipeline functionality in place of the mashup of plugins that we have historically had to use.

          I see dim prospects for further development on these plugins, which have been superseded by Pipeline.

          John McGehee added a comment - - edited At the Jenkins World conference over the past two days, I saw the community moving to the new Pipeline functionality in place of the mashup of plugins that we have historically had to use. I see dim prospects for further development on these plugins, which have been superseded by Pipeline .

            Unassigned Unassigned
            nikem Nikita Salnikov-Tarnovski
            Votes:
            9 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: