sorry for the delay, I've been traveling.
It isn't just the initial installation or recovery from backups, it's also
the ongoing maintenance. Moving all the configs into an SCM would work;
rsyncing works too. But these techniques don't get you a "higher level"
view of the jobs.
For example I have
I think the ability to use an API to update the config of Jenkins would be
great so I'm interested in any answers to this. Right now I'm using Jenkins
Jobs Builder to build all my jobs for me but for certain things, its
hard/impossible to do in a controller manner.
For instance if I add a new job
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 wrote:
> I currently have a set of scri
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% a
