Hi there, On Thu, 13 Apr 2017, at 13:25, David Aldrich wrote: > We use the traditional 'Freestyle' job style for most of our Jenkins > jobs. We also use the 'Freestyle multi-branch project' for some jobs. I > note that the Multi-Branch Project Plugin is now deprecated, so I think > now is the time for us to seriously look at moving to Pipeline jobs. > > The 'New Item' page states that a 'Pipeline' job 'Orchestrates long > running activities that span multiple build slaves'. Our jobs don't fit > that description - they aren't necessarily long and certainly don't span > multiple slaves. I guess I'm saying that we don't need 'staging'. Is > Pipeline still the recommended way for us to go?
I guess that's not the greatest description — it describes what *is* possible (in contrast with Freestyle), but you don't necessarily have to do such things with it. Pipeline is the recommended way to go, even if you don't need to orchestrate large build pipelines, but it has a variety of other benefits: https://jenkins.io/doc/book/pipeline/#why > What is the best way to get started with Pipeline jobs? Do I need to > learn the scripting language or should I use Blue Ocean to generate the > jobs graphically? Go through that documentation link to get a flavour of what it looks like — you can use the newer Declarative syntax, so you don't necessarily have to learn the Scripted syntax. Or use the Blue Ocean visual editor; it will generate the same declarative syntax for you. > Finally, we use svn exclusively, not git. Will that cause us any > problems? Nope, the SVN plugin has Pipeline support. Regards, Chris -- 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/1492083843.288602.943536008.703C4D92%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
