One of the components of the workflow system is a plugin that provides a global git repository where you can push your groovy build scripts. https://github.com/jenkinsci/workflow-plugin/tree/master/cps-global-lib
This is really quite nice because you can develop your build workflow in groovy in a way that feels very good to me as a developer -- I started out with a single script that combined a few of the steps together, but very quickly started adding a JiraClient class and then JiraIssue class and then a GitHubCommitStatus class and a HipChatClient class and you can wrap everything up together in a way that makes the UI feel very clunky. --Alex On Wednesday, December 31, 2014 9:02:38 PM UTC+1, David Karr wrote: > > I haven't looked at an installation using the Workflow plugin, but I have > a question or two. > > I get the impression that the script used in a workflow job can be loaded > from SCM, instead of hardcoded into the Jenkins job. How exactly do you > specify that? I noticed the "load" workflow step, but that's not quite the > same thing. > -- 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/8ef64bf8-a291-488e-8caf-fcaac17c9ad8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
