Well I already had to fix one of the Trigger implementations to switch from AbstractProject to Item... so be warned... plus 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... the other reason is that I think it is a UI disaster and build config should be part of the source code not separate from it)
On 19 May 2014 15:03, Jesse Glick <[email protected]> wrote: > On Sun, May 18, 2014 at 4:42 AM, Stephen Connolly > <[email protected]> wrote: > > you may need it to be Item if you are working with […] multi branch > project types. > > I.e., a MultiBranchProject, which is not a Job. True, although I doubt > that descriptor web methods of most plugins would be able to work out > of the box with a freestyle multi-branch project to begin with, and > typically they would be unnecessary in a literate project. > > Anyway I filed https://rm.cloudbees.com/issues/2433 to try to make > this safer in the Templates plugin. > > -- > 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.
