Re: Abstract type and groovy syntax

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 < jenkinsci-dev@googlegroups.com> wrote: > Hello, > > I need to convert a

Re: Abstract type and groovy syntax

Here is the field I am talking about: Here is how it os currently used:

Re: Migrating username & secret password to credentials plugin

> On 8. Jan 2022, at 13:59, 'Réda Housni Alaoui' via Jenkins Developers > wrote: > > Is there a best practice for this kind of data migration? What should I do > with the old field data? Should I automatically create one credentials > instance per legacy username & password in a new

Re: Migrating username & secret password to credentials plugin

Email Extension did this recently in jenkinsci/email-ext-plugin#325 and the follow-up bug fix jenkinsci/email-ext-plugin#332. -- 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

Migrating username & secret password to credentials plugin

Hi all, https://github.com/jenkinsci/sonar-gerrit-plugin/blob/905786a87ab70b3af130ea718472f05511efd650/src/main/java/org/jenkinsci/plugins/sonargerrit/config/GerritAuthenticationConfig.java#L25 is currently storing some credentials in 2 fields: - String username - Secret password I'd like to

Re: Migrating username & secret password to credentials plugin

Thank you all. I think I am going to take the automatic migration road. Le samedi 8 janvier 2022 à 17:54:34 UTC+1, m...@basilcrow.com a écrit : > Email Extension did this recently in jenkinsci/email-ext-plugin#325 > and the follow-up bug fix jenkinsci/email-ext-plugin#332. > -- You received

Abstract type and groovy syntax

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