Hello,
We invest so much time and effort into maintaining Jenkins jobs, I fear
that my organization would be dead in the water if Jenkins went down.
I'd like a way to extract the build steps from the config files--tuning
them into an executable script.
It seems possible to translate the config
On Tue, Feb 12, 2013 at 1:59 PM, Steve K steve.kerxha...@carestream.com wrote:
Hello,
We invest so much time and effort into maintaining Jenkins jobs, I fear that
my organization would be dead in the water if Jenkins went down.
I'd like a way to extract the build steps from the config
I've actually done the opposite of this to migrate from our internal build
tool to Jenkins a few years ago. The config.xml files that have the build
info are pretty easy to parse if you are looking for a way to do that, any
XML library for any language you are familiar with would make quick work
Once you have your config.xml files backed-up you should be able to restore
your jobs, through Rest API. For old buils, if they are important you
should make other arrangements...
Backing-up entire .jenkins directory, should help too, but you'll need more
space of course.
On Tue, Feb 12, 2013
I'm not sure why you would want yet another way to do it.
Basically for migration and maintenance purposes
1) I've got a set of scripts that can populate my Hudson jobs. So I can
delete all the jobs, re-run my scripts and nearly everything is back to
where it was.
I took those scripts, re-did
