What are you actually trying to accomplish? I mean, if you're starting with a fresh instance (or at least set most of the settings) anyway, what's wrong with checking it out from SCM, rsyncing, or cloning a template VM?
On 08.08.2013, at 22:51, J Arrizza <[email protected]> wrote: > I currently have a set of scripts that I use to get/set all of the job > parameters/settings/configuration. This means that I can take a machine with > vanilla jenkins on it and pretty much recreate everything I care about in all > the jobs. > > But there seems to be a few things missing to make this 100% automated: > - getting a list of plugins and their versions; being able to install > plugins from the API > - setting up views > - setting Global Properies (e,g Environment Variables) > - setting Locks (for the locks and latches plugin) on the "Manage Jenkins" > page > - setting Xnvc (for the xvnc plugin) on the "Manage Jenkins" page > - setting Jenkins Location information and admin email info > - setting email notification information > - setting up Nodes > > I can take the "low road" and use scp to get the config.xml, modify it and > push it back, but before I do that, is there any chance this kind of access > is in future plans for Jenkins? > > Thanks > John > > > -- > 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. > > -- 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.
