I do not think the Freestyle version has any merit what so ever. So
refusing to publish it is doing the community a service in my opinion. It's
not like you can't see the code yourself and decide to push it if you
wanted to (or KK for that matter)

The point I was making is that there is at least one implementation of the
multi-branch where Builders and Publishers are used... thus it is
conceivable that others may develop a multi-branch that is a hybrid of the
completely borked Freestyle multibranch and the completely SCM based
literate job type. It would not surprise me if such a hybrid needed
Builders or Publishers to expect Item as a common parent class.

(one idea of such a hybrid is to force the exact same builders and
publishers on all branches... that at least is less confusing than the
"default" plus customizations on a per-branch basis that my Freestyle
Multibranch job type gives... and that UI complexity is why I invented the
literate job type ;-) )


On 19 May 2014 15:23, Jesse Glick <[email protected]> wrote:

> On Mon, May 19, 2014 at 10:12 AM, Stephen Connolly
> <[email protected]> wrote:
> > the FreestyleMultiBranchProject type that KK keeps wanting me to release
> is
> > broken unless people use Item and not AbstractProject in their Builders
> and
> > Publishers (the broken ness of it is one of the reasons why I don't want
> to
> > release the Freestyle multi-branch project type
>
> If you refuse to even publish the source code, no one has a chance to
> improve it, or test their plugins against it!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to