On Tuesday, May 21, 2013 1:11:57 AM UTC-7, matthew...@diamond.ac.uk wrote:
>
> I often find the low-tech approach works. For simple bulk changes I edit
> the config.xml files using the bash command line (this is Linux,
> obviously). Something like this:
>
>
>
> cd /path/to/Jenkins-home/jobs/
>
> find -mindepth 1 -maxdepth 1 -type d -name "jobname.pattern.of.interest* "
> | sort | xargs -i --verbose sed --in-place
> 's#delete_materialize_on_completion=true</propertiesContent>#delete_materialize_on_completion=false\nbuckminster_result_delete=true</propertiesContent>#g'
>
> {}/config.xml
>
>
>
> You need to check the result carefully, of course. More complex changes
> could probably be done using a simple python script.
>
>
>
> Hope that helps
>
> Matthew
>
>
>
> *From:* jenkins...@googlegroups.com <javascript:> [mailto:
> jenkins...@googlegroups.com <javascript:>] *On Behalf Of *Bob Bick
> *Sent:* 20 May 2013 22:45
> *To:* jenkins...@googlegroups.com <javascript:>
> *Subject:* Mass Jenkins job updates
>
>
>
> Hi,
>
>
>
> We have many Jenkins jobs defined that were copied from a “template”
> Jenkins job. Now, I discovered that I’d like to add a new build step to
> most (not all) of the jobs.
>
>
>
> There seems to be several ways to modify the jobs:
>
> 1) *Brute force* – Edit each job by clicking the Jenkins “Job
> Configure” button for each job. (Yuck)
>
> 2) *Groovy Script Console *- This has the downside that I could
> screw up the configurations if I have a bug in the groovy script.
>
> 3) *Job DSL Plugin*
>
> 4) *Jenkins Enterprise Templates* – Not really sure whether this can
> even be done.
>
> 5) *Manually edit config.xml files*
>
> 6) *Other???*
>
>
>
> Before investing time in coming up with a solution, I would like to know
> how other people have addressed mass updates to Jenkins jobs; and what
> worked well (or not so well).
>
>
>
> Any feedback/guidance would be much appreciated.
>
>
>
> Thanks,
>
>
>
> Bob
>
>
>
>
>
>
> --
>
> This e-mail and any attachments may contain confidential, copyright and or
> privileged material, and are for the use of the intended addressee only. If
> you are not the intended addressee or an authorised recipient of the
> addressee please notify us of receipt by returning the e-mail and do not
> use, copy, retain, distribute or disclose the information in or attached to
> the e-mail.
> Any opinions expressed within this e-mail are those of the individual and
> not necessarily of Diamond Light Source Ltd.
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any
> attachments are free from viruses and we cannot accept liability for any
> damage which you may sustain as a result of software viruses which may be
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England
> and Wales with its registered office at Diamond House, Harwell Science and
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>
> This is also my approach. For simple changes, I edit the config.xml files
> directly. It is usually easy to figure out what needs to change from the
> context. That it's flat text makes it quick to edit and review. This does
> require a "Reload Configuration from Disk" after the edits are made.
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
