I viewed it in exactly the opposite direction. If using a freely available, easily installed external program allows the plugin to be implemented faster and cleaner and simpler, then I'd rather have it implemented sooner with the external program. I suspect that specifying a graph in graphviz is much simpler and more reliable than creating the Java and HTML code necessary to do the same thing in Java or HTML.
If the original implementer of the git plugin had decided that he must not use external programs, it would likely have delayed the git plugin by months or years while waiting for a sufficiently complete native java implementation of git. There are many SCM systems (and other tools) which are only available as external programs, so I don't think we'll be able to avoid referencing external tools from a continuous integration server. Mark Waite >________________________________ > From: kikou <ingenieur.high.t...@gmail.com> >To: jenkinsci-users@googlegroups.com >Cc: Mark Waite <markwa...@yahoo.com> >Sent: Wednesday, September 26, 2012 6:16 AM >Subject: Re: Automatic diagram > > >Hello >sorry for this late answer > >I didnt pay attention but indeed it is working >Nevertheless i found pity that we need another graphical lib, i am sure that a >plugin could be done with java tools only or html object, i really prefer a >plugin which not needs external binaries. > >K. > >Le mercredi 5 septembre 2012 15:23:40 UTC+2, Mark Waite a écrit : >We use that plugin very frequently and it works great for us. Why do you say >"what a pity that this plugin is not maintained"? We've not found any cases >where it had bugs or issues that blocked our work, and I don't recall any >recent complaints from other users either. >> >>Can you describe further why you think it might need an update? >> >>Mark Waite >> >> >>From: kikou <ingenieur...@gmail.com > >>>To: jenkins...@googlegroups. com >>>Sent: Wednesday, September 5, 2012 5:20 AM >>>Subject: Re: Automatic diagram >>> >>> >>>Hi Gergo >>> >>>Thank you. The plugin you gave is exaclty what i am looking for. >>>I maybe do a missunderstanding but it is the dependancy indeed i'd like to >>>have in a graph showing the sequence of projects (not build number), in >>>other words seeing upstream and downstream projects in one graph. >>> >>>what a pitty that this plugin is not maintained. Yes maybe i could update it >>>but not now. >>> >>>Thank you a lot Gergo >>> >>>Rgds >>>K. >>> >>>Le mercredi 5 septembre 2012 12:15:51 UTC+2, Gergo a écrit : >>>Hi, >>>>You mention "job sequence" but if you mean "build sequence" - I don't think >>>>it's predictable/static as it depends on dynamic factors (e.g availability >>>>of slaves, build duration changes affect allocation). >>>>Not exactly sure about your requirements, but I'm using Dependency Graph >>>>View: http://wiki.hudson-ci. org/display/HUDSON/Dependency+ >>>>Graph+View+Plugin , this seems to be how far you can get solely looking at >>>>the jobs. >>>> >>>> >>>>hth, >>>>Gergo >>>> >>>> >>>>On Wed, Sep 5, 2012 at 8:14 AM, kikou <ingenieur...@gmail.com > wrote: >>>> >>>>Hi all >>>>> >>>>>Is there any plugin which draw automatically a diagram showing the job >>>>>sequence ? >>>>>So that it is more easy to show to some people the >>>>> >>>>>i dont like the format of pipeline view and it is more to show the result >>>>>of last builds than the sequence. >>>>> >>>>> >>>>>Rgds >>>>>K. >>>>> >>>> >>> >>> > >
