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 of them.
On Tue, Feb 12, 2013 at 1:13 PM, Les Mikesell <[email protected]> wrote: > On Tue, Feb 12, 2013 at 1:59 PM, Steve K <[email protected]> > 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 files--tuning > them > > into an executable script. > > It seems possible to translate the config file into a shell script or > batch > > file. > > Has anyone already done this? > > > > Most of our build steps simply run scripts that are checked in with > the source and work the same in jenkins as a developer's desktop. > But, we also keep the jenkins system backed up so it wouldn't be too > hard to spin up a new machine as a replacement if needed. I'm not > sure why you would want yet another way to do it. > > -- > Les Mikesell > [email protected] > > -- > 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. > > > -- Website: http://earl-of-code.com -- 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.
