On Thu, Jan 4, 2018 at 8:17 PM, Sharon Grubner <[email protected]> wrote:
> as part of our DSL libraries we like to set up different utilities that lead
> to more consistent pipeline jobs across our different projects/users.
The normal way to accomplish that is to use Pipeline libraries, so the
first example is a strawman. A more realistic comparison would be to
something like
pipelineJob('example') {
definition {
cps {
script('''
library 'the-usual-stuff'
theUsualBuild repo: '…',
label: 'windows',
artifacts: '*.e*,*.o*'
''')
sandbox()
}
}
}
(In such a case, if you want to try changes to the logic, you can just
use the Replay feature in the UI until you get it right, after which
you have a diff which could be applied directly to the Job DSL script
and/or the library definition.)
Anyway, if you have some use case for a builder like this, the usual
approach is to publish on your GitHub account and try to find others
who wish to use it. Probably it could be packaged as a plugin
depending on the SPIs in `job-dsl`.
--
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/CANfRfr2Wj72Df3zr9xzqJXZyjY0qMDLb%3DgRC8nCeU0iu7N%3DYEA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
