Here is the field I am talking about:
<https://github.com/jenkinsci/sonar-gerrit-
plugin/blob/20e9cff705d15708824f6d7897c372ee1467f5d3/src/main/java/org/jenkinsci/plugins/sonargerrit/SonarToGerritPublisher.java#L67>

Here is how it os currently used: <https://github.com/jenkinsci/sonar-
gerrit-plugin/blob/master/README.md#pipeline-overridden-settings-
example>

I guess your answer only makes sense for the name of the step, not for a
field inside the step.

On January 8, 2022, Tim Jacomb <[email protected]> wrote:
> Best to send code examples if you can
>  specifying a @Symbol(“stepName”) on the descriptor of the step will
> remove the need for the class syntax
> On Sat, 8 Jan 2022 at 20:53, 'Réda Housni Alaoui' via Jenkins
> Developers <[email protected] <mailto:jenkinsci-
> [email protected]>> wrote:
> > 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]
> > <mailto:[email protected]>.
> >  To view this discussion on the web visit
> > https://groups.google.com/d/msgid/jenkinsci-
> > dev/d70fb6a46b6073b39d7afcc38ed84717de76b11c%40hey.com
> > <https://groups.google.com/d/msgid/jenkinsci-
> > dev/d70fb6a46b6073b39d7afcc38ed84717de76b11c%40hey.com?utm_medium=email&utm_source=footer>.
>
>  -- 


>  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/0vO5q_Cl414/unsubscribe>.
>  To unsubscribe from this group and all its topics, send an email to
> [email protected] <mailto:jenkinsci-
> [email protected]>.
>  To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifHX1g5%2B-Z4Gf-
> 1BydLBxZwOVzvPN_dEmM0nBeyAeNw7Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifHX1g5%2B-
> Z4Gf-
> 1BydLBxZwOVzvPN_dEmM0nBeyAeNw7Q%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
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/2b2ae6e02324f00ad72843dc8d88a7f245f8dd5e%40hey.com.

Reply via email to