1. Job DSL is not part of Jenkins core so it would have a separate docset. 2. When we have a Jenkins server to hand we do generally try to use the Pipeline syntax / snippet generator. But sometimes we’re dealing with Jenkins servers that may be behind firewalls - or fixing non-functional servers - such that we can’t use the interactive documentation. Lots of developers also just don’t know about the interactive docs. As a result we still often use the static pipeline docs.
Chris On Wed, 22 Jan 2020, at 6:01 PM, Jesse Glick wrote: > On Wed, Jan 22, 2020 at 10:43 AM Chris Kilding > <[email protected]> wrote: > > Jenkins admins in my company utilise the Pipeline DSL reference and the > > JobDSL reference quite heavily - these are the things we’d most like to > > have in an offline docset. > > Not sure offhand about `job-dsl`, but the Pipeline DSL is better > referenced within the product itself, e.g. > > https://ci.jenkins.io/pipeline-syntax/ > > which takes into account the precise versions of installed plugins, > and gives much more information than the static HTML could. > > -- > 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/CANfRfr3aK%2BPPwadfPpDKHHyFLY_F5gqKM%3DiBus9VKyH2U5n3HQ%40mail.gmail.com. > -- 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/a73741b8-8ad3-4b98-9c06-bd82e6cb75f3%40www.fastmail.com.
