If by same DSL, you mean the pipeline script (DSL) - yes, you can do stand alone pipeline jobs, that aren't tied to any specific repo (and aren't multibranch aware). They can be triggered via various means, take parameters etc.
But I may be misunderstanding the question. Another pattern I have seen in the wild is that there is a separate repo for the more infra-related concerns, with its own Jenkinsfile, that runs as needed, taking the upstream artifacts that other repos have produced (via their respective pipelines). On Wednesday, June 29, 2016 at 3:23:50 AM UTC+10, Alex Ehlke wrote: > > We've been interested in having multiple "pipelines" per repo primarily > for operational tasks that are independent of delivery. A couple examples: > daily logical backups; some jobs that are manually triggered to manage > production services in the event of an outage. If it's the case that > Jenkinsfile isn't meant to address these types of jobs (which would > otherwise make sense to live within the repo whose service they pertain > to), then it's disappointing to lose out on its way of defining jobs. It'd > be great to have one way to define jobs whether or not they're in a repo's > (or branch's) singular pipeline, rather than relying on a combination of > Jenkinsfile and Netflix's Job-DSL for other jobs, for instance, and ending > up with disparate job DSLs. > > Is there something I'm missing? Is there a way to define "standalone" jobs > with the same DSL that Jenkinsfile uses? Or are those left to remain > outside of source control (or to some entirely different tool)? > > On Monday, May 30, 2016 at 7:14:53 PM UTC-4, Michael Neale wrote: >> >> One jenkinsfile is one "pipeline" - what you may have done with many jobs >> in the past can be done with one pipeline. it can be quite rich if you need >> it to be. >> >> You can call other "jobs" from a Jenkinsfile, but I am not sure if that >> is what you mean. >> >> >> >> On Monday, May 30, 2016 at 3:47:40 AM UTC+10, Bartłomiej Sacharski wrote: >>> >>> I'm really hyped about the Jenkinsfiles - they make it much much easier >>> to document and preserve project configuration. >>> However, all the examples that I've seen seem to use single pipeline. >>> I've tried to define different stages in separate node blocks, however >>> they still were seen as a single pipeline. >>> >>> Is it possible to define multiple pipelines in a single Jenkinsfile? Or >>> maybe there's undocumented functionality for .jenkinsfile extension to >>> handle such cases? >>> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ee5808b1-1f6a-4482-85b8-270b809ee61c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
