forked as https://github.com/jenkinsci/coordinator-plugin
2012/12/16 nicolas de loof <[email protected]> > > > 2012/12/16 Ace Han <[email protected]> > >> Hello All, >> >> I'm surprised that this kind of plugin got so many comments. That >> flattered me. >> >> As we can review source code we all hope this plugin to be the definitive > silver bullet ;) > > > >> 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 [?] >> > > Can fork, but wonder there is no code there ! > > >> >> 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/**a<http://github.com/vanderhallenf/eloyente.git> >>>> ce-han/coordinator >>>> >>>> Draft version is done, but would like to do some code refactor to make >>>> it beautiful^_^ >>>> >>>> Attachment a snapshot for your reference. >>>> >>>> <https://lh5.googleusercontent.com/-tlPAjoOq0ZU/UMmY72jQ2BI/AAAAAAAAAAw/drfyq3VRjlA/s1600/demo.png> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Is it possible to create a repository to host this plugin? >>>> >>>> Best regards, >>>> Ace >>>> >>>> >>>> >>> >> >
<<338.gif>>
