Hello there,
Recently, I finally rolled out this plugin for release 1.0.0
There is a problem when I'm doing *mvn release:prepare release:perform *I
got below error:
ace@acebuild:~/workspace/github/coordinator$ mvn release:prepare
release:perform
[INFO] Scanning for projects...
[INFO]
2012/12/16 Ace Han ace.jl@gmail.com
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
forked as https://github.com/jenkinsci/coordinator-plugin
2012/12/16 nicolas de loof nicolas.del...@gmail.com
2012/12/16 Ace Han ace.jl@gmail.com
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
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
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
This looks very similar to the Build Flow plugin (although much prettier!).
Is there overlap?
On Thursday, December 13, 2012 4:00:16 AM UTC-5, Ace Han wrote:
Hello,
We have been working on a new Jenkins plugin, which coordinates children
jobs defined within to be executed in a serial or
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/ahttp://github.com/vanderhallenf/eloyente.git
ce-han/coordinator
Draft
