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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ffb284ce-0315-4f5d-adb6-72c20363e673%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
