I generally use Jelly views by default, but switch to Groovy if the
view really needs some complex logic in it: something beyond accessing
public properties of Java objects and doing simple if-then tests.
Really I would prefer a different view engine altogether, based on
`src/main/java/**/*.java`
I hope Jacqueline didn't expect a flame war ;)
As Kanstantsin and Stephen points out is that Jelly is better if you are a
beginner because there is better documentation, more examples to draw from
and the syntax itself is closer to html, so often simpler to debug with an
ocular inspection. And the
On 10 September 2015 at 00:35, Kanstantsin Shautsou <
kanstantsin@gmail.com> wrote:
> 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 c
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
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 tim
Well, if you are new in jenkins, then i can suggest using jelly. When you
know how UI constructs you will understand where Groovy wins. But for new
comers groovy will be very difficult as it not documented at all for some
controls.
On Thursday, September 10, 2015 at 12:41:00 AM UTC+3, Jacquelin
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
