search

ganesansays / build-pipeline-plugin

Automatically exported from code.google.com/p/build-pipeline-plugin
0 stars 0 forks source link

Join plugin does not show correctly #21

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 

When you have job that triggers say 3 jobs as post build step and then one 
final job as Join Trigger job build pipeline show last job 3 times. one 
continuing from each of previous jobs instead of only once. Also history view 
show all jobs pending from that point on, even that jobs are finished in 
reality.

Jenkins version 1.404
build-pipeline-plugin 1.1.1
join-plugin 1.9

Original issue reported on code.google.com by savita...@gmail.com on 14 Apr 2011 at 9:34

GoogleCodeExporter commented 9 years ago 
As per the release notes for v1.1.1 
(http://www.centrumsystems.com.au/blog/?p=165) support for the Join plugin is 
listed as a known issue and slated as future work.

Thanks for the feedback.

Original comment by kev...@centrumsystems.com.au on 14 Apr 2011 at 11:34

GoogleCodeExporter commented 9 years ago 
We would also like to see this feature implemented since we are using join with 
build pipeline.

Original comment by cron...@gmail.com on 19 Sep 2011 at 5:33

GoogleCodeExporter commented 9 years ago 
I've a working implementation of join support at 
http://code.google.com/r/nicolasdeloof-build-pipeline-plugin/source/browse, 
thanks to API exposure in join-1.3 and recent changes in jenkins core

Original comment by nicolas....@gmail.com on 2 Oct 2011 at 10:13

GoogleCodeExporter commented 9 years ago 
Hi Nicholas, I'm really interested in this enhancement. Will your changes make 
it into the official build-pipeline-plugin anytime soon?

Thanks

S

Original comment by shabera...@gmail.com on 4 Oct 2011 at 2:44

GoogleCodeExporter commented 9 years ago 
I can't say if my changes will be merged in the official plugin, they are 
designed to, but there is no "pull request" on GoogleCode / Hg :P

Original comment by nicolas....@gmail.com on 4 Oct 2011 at 7:45

GoogleCodeExporter commented 9 years ago 
Ok thanks. I tried to compile yours however there are various failures. Is your 
version complete?

Original comment by shabera...@gmail.com on 4 Oct 2011 at 10:19

GoogleCodeExporter commented 9 years ago 
Version is complete, what failure do you encounter ? Can we follow this on 
jenkins-dev list please ?

Original comment by nicolas....@gmail.com on 7 Oct 2011 at 12:21

GoogleCodeExporter commented 9 years ago 
Nicolas, we'd love to incorporate your changes!   We've been a bit lax 
recently, but hope to get a chance to do another release in the next couple of 
months.  

Would you be able to put some brief doco and screenshots together that we can 
include when we release it?

Original comment by geo...@centrumsystems.com.au on 9 Oct 2011 at 9:35

GoogleCodeExporter commented 9 years ago 
Hi,

here is a screenshot of the plugin rendering a A - Join( B, C, D) - E project 
setup

Original comment by nicolas....@gmail.com on 13 Oct 2011 at 12:02

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi, I've managed to build it, and it works as you've shown above - which is 
great. However, the problem is that the "pending" jobs still get rendered, and 
with a more complex dependency graph, the number of "pending" jobs becomes very 
large very quickly.

Is this something that can be resolved easily? 

Can continue discussion here - 
http://groups.google.com/group/jenkinsci-dev/browse_thread/thread/e411698c33622d
3f

Thanks!
S

Original comment by shabera...@gmail.com on 13 Oct 2011 at 1:47

GoogleCodeExporter commented 9 years ago 
Sure, the same principle used for grouping jobs can apply for grouping builds.

Original comment by nicolas....@gmail.com on 14 Oct 2011 at 5:56

GoogleCodeExporter commented 9 years ago 
Integration of this feature in the Build Pipeline plugin would be very much 
appreciated. Let me know if there is a way for me, as a programmer, to help 
getting this into everybody's hands...

Original comment by er...@pensioenpage.com on 12 Nov 2011 at 7:35

GoogleCodeExporter commented 9 years ago 
Issue 20 has been merged into this issue.

Original comment by geo...@centrumsystems.com.au on 27 Nov 2011 at 1:07

GoogleCodeExporter commented 9 years ago 
1.2.4 is available for manual download and testing:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin+-+Roadmap

Original comment by geo...@centrumsystems.com.au on 27 Nov 2011 at 7:43

GoogleCodeExporter commented 9 years ago 
1.2.4 is available for manual download and testing:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin+-+Roadmap

Original comment by geo...@centrumsystems.com.au on 27 Nov 2011 at 7:44

GoogleCodeExporter commented 9 years ago 
1.2.4 is available for manual download and testing:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin+-+Roadmap

Original comment by geo...@centrumsystems.com.au on 27 Nov 2011 at 7:45

GoogleCodeExporter commented 9 years ago 
1.2.4 is available for manual download and testing:
https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin+-+Roadmap

Original comment by geo...@centrumsystems.com.au on 27 Nov 2011 at 7:55

GoogleCodeExporter commented 9 years ago 
It would be great to support visualizing jobs created by the 'Build Flow' 
plugin. This is an alternative / more powerful way to parallelize jobs vs. 
'Join' plugin.

The visualization would look the same, I guess.

Original comment by bgolding...@gtempaccount.com on 19 Apr 2012 at 10:03

GoogleCodeExporter commented 9 years ago 
I created a clone with a very simple fix for this issue. Since the fix is not 
sophisticated, it might not work for everybody, but it definitely reduces the 
clutter in the pipeline view.

The changes are as follows: and PENDING builds that are children of a Join are 
hidden from the pipeline view. Nothing is different for projects without Join 
jobs, and the plugin still works for Jenkins instances without the Join Plugin 
installed.

More info, plus an HPI for download, here: 
http://code.google.com/r/jessica-join-support-build-pipeline-plugin/

Original comment by jess...@aus10.org on 29 Dec 2012 at 5:54

GoogleCodeExporter commented 9 years ago 
I agree with comment #18 the build flow plugin offers a VERY powerful DSL that 
allows a more powerful "pipeline". Visualization of that would be GREAT.

Original comment by Christop...@gmail.com on 5 Feb 2013 at 12:02

GoogleCodeExporter commented 9 years ago 
Hi, is the patch from Nicolas to allow Join Job to show correctly on the graph 
already in the latest build (1.3.3) of Build Pipeline?  I am still seeing the 
Join Job displayed as many times as there up upstream jobs joining into it.

Thanks!

Original comment by tsail...@gmail.com on 12 Mar 2013 at 5:40

GoogleCodeExporter commented 9 years ago 
If there is patch available, what is holding it back from being applied? This 
bug is still present in current version.

Original comment by gni...@gmail.com on 23 Jul 2013 at 12:35

GoogleCodeExporter commented 9 years ago 
I'd like to add my name to the list of people eagerly awaiting the fix for this 
issue

We are working with a build pipeline with some quick time wins in terms of 
fork-joins, but with the current behaviour we would end up with a completely 
unintelligible graph.

Original comment by verhagen...@gmail.com on 29 Jul 2013 at 7:54

GoogleCodeExporter commented 9 years ago 
i too would like the patch to be included. we have quite a complex pipeline 
with loads of joins and the clutter really makes the graphs unintelligible. 

so adding my name to the list also.

Original comment by y...@varnish-software.com on 26 Sep 2013 at 7:58

GoogleCodeExporter commented 9 years ago 
I'd like to propose my help on this issue.

Is Nicolas contribution accessible somewhere in a recent build pipeline git 
branch? I tried to create a patch of the contribution from the Hg repo to apply 
it on the new git repo, but there are too much conflicts to easily merge it in 
the head of git master branch.

What prevented the integration of Nicolas contribution by the time he proposed 
it? What still need to be done for it to be merged in a future build pipeline 
release?

Jessica's contribution looks much more easy to merge for now. Is there any 
reason not to integrate such contribution?

Original comment by gonzague...@gmail.com on 7 Mar 2014 at 10:54

GoogleCodeExporter commented 9 years ago 
This issue is pending for 3 years! Can I help? Is there any workaround?

Original comment by aleksand...@gmail.com on 8 Nov 2014 at 2:58

GoogleCodeExporter commented 9 years ago 
4 years now !!! Still no patch

Original comment by adroboti...@gmail.com on 2 Jul 2015 at 10:27