On Sat, Aug 15, 2020 at 3:42 PM Anton Shepelev <anton....@gmail.com> wrote:
> Gianluca: > > > take into account that the declarative syntax (and in general > > Jenkins pipelines) are just a DSL > > ( https://en.wikipedia.org/wiki/Domain-specific_language ) > > heavily based on Groovy language > > ( http://groovy-lang.org/index.html ). > > So, many (really many) things you can do ... it's just Groovy > > language, like the one you asked. > > Thank you. I know about domain-specific languages, having > programmed in Simula, GPSS, and Prolog, but I wonder why the > Jenkins documentation references that Wikipedia page about DSL's, > which does even mention Groovy, yet fails to reference a document > describing the syntax of Groovy: > > https://www.jenkins.io/doc/book/pipeline/#pipeline-syntax-overview > > That comfused me! If possible, will the maintaners please consider > informing the readers that the declarative syntax is based on > Groovy and direct them to the Groovy specification? > > Thanks for the suggestion. We've had many users that expected Jenkins Pipeline to be Groovy (especially scripted Pipeline users) instead of being a domain specific language that is based on Groovy. I fear that linking to more details of Groovy syntax will tend to confuse those users even more rather than clarify for them. The syntax of Declarative Pipeline is quite specific to Jenkins. Linking from Declarative Pipeline documentation to the Groovy syntax seems to me like it will be more likely to confuse users rather than clarify for them. Declarative Pipeline is well suited for use in the Blue Ocean pipeline editor and in defining Pipelines with Jenkins. I'd rather include specific descriptions of syntax rules for single quote and double quote strings and for variable expansion rather than link to the Groovy documentation. Mark Waite > > In fact, triple quote is documented at > > http://groovy-lang.org/syntax.html#_triple_single_quoted_string > > And also many "command" like "bat" you mentioned in the email are > > just Groovy function and follow the Groovy rules about parameters > > and how you can call them. > > In the case of "bat" is you just pass one parameter is used as > > script, as you pass more than one you need to specify who is what: > > "bat script: "whatever", returnStout: true" > > Thank you. > > -- > () ascii ribbon campaign - against html e-mail > /\ http://preview.tinyurl.com/qcy6mjc [archived] > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/20200816004151.e46885ae9c38872a3d92d65d%40gmail.com > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFG%3DwcJUb7BY4Vy%2BFFjmAr3m0a9mixOGYHob%2B2JJ3wXyQ%40mail.gmail.com.
