On 04/19/2012 11:51 AM, Bap wrote:
As creator of the [Flexible Publish Plugin][1], I think this is an
excellent idea.
The two main drivers for Flexible Publish were:
1. Set the order of execution
2. Allow a publisher to be used more than once
I'm all for removing the single instance of a type restriction - some
publishers do not work when run more than once, but many are more than
happy. We could create a marker interface to enable post-build tasks
to either opt in or opt out of multiple use.
I think we'll let publishers tell core if they want to allow multiple
instances, and we can treat them accordingly.
Many of the issues of using a publisher more than once are due to the
fact that the data binding does not expect there to be more than one
instance in a page, and form submission results in unexpected (mixed
up) configurations. Those plugins just need some view TLC to enable
them to be used sucessfully more than once (ie. in [Promoted
Builds][2] and Flexible Publish)
Of course there are also many post build tasks that cannot (should
not) run multiple times for very good reasons.
Looking forward to trying out the change at the weekend,
Bap.
[1]: https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin
[2]: https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+Plugin
--
Kohsuke Kawaguchi
.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins
