hi ace, don't get us wrong - we are looking forward for your contribution - but this are the kind of questions a normal user would ask when searching through the list of plugins. It would be great if your documentation/wiki would explain what the difference between your implementation and the others is. There must be a reasons why you choosed to write your own plugin and not to use/extend an existing one, what are the shortcomings of the other plugins? - let the users know these reasons too.
btw. nicolas forked your repo, so no reason to not enjoy your holidays :) /Domi On 16.12.2012, at 10:01, Ace Han <[email protected]> wrote: > Hello All, > > I'm surprised that this kind of plugin got so many comments. That flattered > me. > > I'm now taking a 7-day annual holiday. And found myself no access to the > working directory (even though I could, that would cost a great effort and > spoil this lovely holiday). > > I would be back on Dec 24, and share the code in giihub first. > > However, I sincerely hope that we could create a repository to host this > plugin. I'm pretty sure that this one would interest you for coordination of > jobs in jenkns <338.gif> > > Best Regards, > Ace > > > On Sat, Dec 15, 2012 at 10:24 PM, nicolas de loof <[email protected]> > wrote: > join plugin has a limited scope, so I won't include it here > > build-pipeline is only about visualization of a static flow (job order don't > change) > > multijob is to establish such a static flow (if I understood it right) > > build-flow can be used to make the flow completely context-specific, so that > two subsequent runs won't trigger same jobs / order. > it compares with jenkow, with a significantly distinct implementation > > So, I think all those plugin make sense for distinct use-cases, would like to > know more about this one to understand how it fit this growing "job > orchestration ecosystem" > > > 2012/12/15 domi <[email protected]> > This looks nice, but what is the difference to plugins like: > > - https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin > - https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin > - https://wiki.jenkins-ci.org/display/JENKINS/Join+Plugin > - https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin > > although these plugins do it different, it seems that all of these plugins > try to solve the same issue: coordination of jobs > > /Domi > > On 13.12.2012, at 10:00, Ace Han <[email protected]> wrote: > >> Hello, >> >> We have been working on a new Jenkins plugin, which coordinates children >> jobs defined within to be executed in a serial or parallel pattern according >> to user-defined order >> >> This is the github: git://github.com/ace-han/coordinator >> >> Draft version is done, but would like to do some code refactor to make it >> beautiful^_^ >> >> Attachment a snapshot for your reference. >> >> >> >> >> >> >> >> >> >> >> >> Is it possible to create a repository to host this plugin? >> >> Best regards, >> Ace > > >
