Jochen, Here are a couple of approaches. They don’t reach the level of “solved” but food for thought:
Generate the xml from scratch every time. Downside is maintaining the domain-specific language, software, and accounting for the changes from one version of Jenkins to the next (as you mentioned with credentials). Create several Template jobs for each job profile (disabled) in each instance (test, staging, production). Create copy-and-minimally-mutate programs that update only the relevant portions. Downside is similar: maintaining the DSL, the software, and making sure it works with many versions, and also assumes a kind of uniformity in your jobs. Also might be hard to update those already-mutated jobs. Cheers, Jesse From: [email protected] [mailto:[email protected]] On Behalf Of Jochen Hinrichsen Sent: Wednesday, March 18, 2015 7:08 AM To: [email protected] Subject: Promote jobs from test -> staging -> production Dear group, we want to follow the same rules for Jenkins jobs that our software itself must confirm to: development in test, testing in staging, and the official version in a production environment. Copy and paste will always work, but i'm too lazy to do that for the 200+ jobs. Maybe something more git-ish? >From a first glance, i can see that everything credential related is different >in the underlying xml configuration files. So a plain 1:1 copy of a job's >external xml representation will not work. Did someone out here already solve this problem? Thanks in advance Jochen -- 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]>. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/732d0cd3-a3de-4ee2-8c59-3fc96d991659%40googlegroups.com<https://groups.google.com/d/msgid/jenkinsci-users/732d0cd3-a3de-4ee2-8c59-3fc96d991659%40googlegroups.com?utm_medium=email&utm_source=footer>. For more options, visit https://groups.google.com/d/optout. ________________________________ The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/736C8F179EBDE343B1EA3BCCEDCB60CA15AE7A02%40BLUPRD6101MB004.025d.mgd.msft.net. For more options, visit https://groups.google.com/d/optout.
