Hi Phil, There is also the Job DSL plugin[1] and Cloudbees Templates[2]. The DSL plugin (not used it) can store the DSL in source control - you can add the Cloudbees templates (done it) to an SCM like git and commit & push them after you make any changes.
/James From: [email protected] [mailto:[email protected]] On Behalf Of phil swenson Sent: 21 February 2014 15:15 To: jenkinsci-users Subject: best approach to automate/manage jenkins jobs? Hi, we have a large number of jenkins jobs and would like to automate and version control their configuration. >From what I can tell, most people just manually config their jobs via the UI. >Unless there are only a few very simple jobs, this leads to an unmanageable >mess. I think the jobs should be coded in a DRY fashion, version controlled, and deployed via a scripted system. Here are the approaches I am aware of: 1) scripting via command line (jenkins cli) 2) scripting via the rest web services 3) chef cookbook http://community.opscode.com/cookbooks/jenkins What are most people doing? Any recommendations? thanks phil -- 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]<mailto:[email protected]>. For more options, visit https://groups.google.com/groups/opt_out. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
