Hello,

I need to convert a build step configuration field from a concrete to an
abstract type with 2 sub types.  I have 2 groovy related questions.

1- I want to make sure the pipeline syntax is as simple as possible. Is
$class groovy attribute usage mandatory in such a case? If not, what
would be a simpler syntax?

2- If the $class syntax is mandatory, how to make it backward compatible
with existing scripts that expects a single concrete type without
$class. Is there a way to designate a default implementation which would
be used in the absence of $class?

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d70fb6a46b6073b39d7afcc38ed84717de76b11c%40hey.com.

Reply via email to