Jelly like xml has overhead, that’s why workflow/build flow/gradle produces DSLs. Groovy code is clean and has less tags, supported by IDE and allows setting breakpoints for debug. Also it provides more control under page internals (that is also penalty in conjunction with lack of docs). I never had performance issues. As i understand both is runtime compilable. Stephen please provide some performance example if you hit it. I think nowadays it shouldn’t have such issues.
> On Sep 10, 2015, at 01:20, Stephen Connolly <stephen.alan.conno...@gmail.com> > wrote: > > Use jelly always. It is closer to the html. It is more obvious what the > effects will be. It is faster. > > The only reason to use groovy view is if you want partial support for IDE > completion of expressions (it's only partial mind, as the IDE will not be > able to get full contextual type info) > > Any time I find a view performance issue it is usually a groovy view and > reworking as jelly usually yields a simpler file with better performance. > > But that is my personal experience and I've been writing jelly views since > 2006... The groovy fanboys have not been able to convince me to switch yet. > > (I would switch to handlebars as a templating engine, some day soon I'll bite > the bullet and implement support for handlebars as a view rendering engine in > stapler) > > On Wednesday, September 9, 2015, Jacqueline Taing <jgta...@dssd.com > <mailto:jgta...@dssd.com>> wrote: > Hi, > > I am fairly new to plugin development and I would like to understand when > someone would use jelly vs. groovy script for the UI. I am seeing some > plugins with jelly but some that use groovy. When would you use one over the > other? > > Thanks, > -jacqui > > -- > 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 jenkinsci-dev+unsubscr...@googlegroups.com > <javascript:_e(%7B%7D,'cvml','jenkinsci-dev%2bunsubscr...@googlegroups.com');>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/37090e7c-5188-4c94-ab57-1c20dfcad0a4%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/37090e7c-5188-4c94-ab57-1c20dfcad0a4%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > Sent from my phone > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/n4Xw9pq2fl8/unsubscribe > <https://groups.google.com/d/topic/jenkinsci-dev/n4Xw9pq2fl8/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-dev+unsubscr...@googlegroups.com > <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxJe74ZSFeoSN%2BChVbY8n3-r4N2A4suR4uzsAjOcM1V_A%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxJe74ZSFeoSN%2BChVbY8n3-r4N2A4suR4uzsAjOcM1V_A%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C946105A-8466-4383-B875-1B58F57879FF%40gmail.com. For more options, visit https://groups.google.com/d/optout.
