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/
On Monday, May 20, 2013 5:44:48 PM UTC-4, Bob Bick wrote:
>
>
> 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.
>
I used the Job DSL plugin for a while but that turned
ring the template
> attributes. This makes using Groovy code not very useful since it can’t be
> dynamic.
>
>
>
> Bob
>
>
>
> *From:* teilo [mailto:teilo+...@teilo.net ]
> *Sent:* Tuesday, May 21, 2013 5:39 PM
> *To:* jenkins...@googlegroups.com
> *Cc
: jenkinsci-users@googlegroups.com
Cc: 'teilo'; Bob Bick
Subject: Re: Mass Jenkins job updates
its just someAttribute not $someAttribute (although my groovy isn't the best
and $someAttribute could also be correct syntax :/ )
You need to make sure that the template creates valid XML th
if it is
> possible to access attribute values in the Groovy template code?
>
>
>
> Thanks in advance.
>
>
>
> Bob
>
>
>
>
>
>
>
>
>
> *From:* teilo [mailto:teilo+...@teilo.net ]
> *Sent:* Tuesday, May 21, 2013 9:11 AM
> *To:* j
that correct? Or, maybe
there is a way to define a default value that all jobs would get?
Bob
From: teilo [mailto:teilo+...@teilo.net]
Sent: Tuesday, May 21, 2013 8:59 AM
To: jenkins...@googlegroups.com
Cc: Bob Bick
Subject: Re: Mass Jenkins job updates
Hi Bob,
"Just so I understand w
? Or,
> maybe there is a way to define a default value that all jobs would get?
>
>
>
> Bob
>
>
>
> *From:* teilo [mailto:teilo+...@teilo.net ]
> *Sent:* Tuesday, May 21, 2013 8:59 AM
> *To:* jenkins...@googlegroups.com
> *Cc:* Bob Bick
@googlegroups.com
Cc: Bob Bick
Subject: Re: Mass Jenkins job updates
Hi Bob,
"Just so I understand what you are saying... If you create a job based on a
template, and then you make a change to the template, all jobs are
automatically updated based on the template?"
Yes - if your jobs are bas
Hi Bob,
"Just so I understand what you are saying... If you create a job based
on a template, and then you make a change to the template, all jobs are
automatically updated based on the template?"
Yes - if your jobs are based on that template then they are all
automatically updated.
"I
Thank you for the response.
Just so I understand what you are saying... If you create a job based on a
template, and then you make a change to the template, all jobs are
automatically updated based on the template? I have not tried this; however, I
would assume that you'd need to modify the tem
Bob Bick netjets.com> writes:
>
>
>
> 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)
> Br
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
12 matches
Mail list logo
