Using Groovy via the Jenkins console is probably a better way to go.
There's a whole bunch of samples on the wiki
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Script+Console and
linked sites so you should be able to easily whip something up.

Richard.


On Fri, Jul 12, 2013 at 5:56 AM, Bob Bick <[email protected]> wrote:

>  Hi,****
>
> ** **
>
> I am finding myself wanting to “grep” through Job configuration files
> (config.xml files) almost on a daily basis. For example, I’d like to see
> all jobs that are using the hudson.plugins.cobertura.CoberturaPublisher
> plugin.****
>
> ** **
>
> It is a hassle to “grep” the config files and I was wondering if there is
> a better way to do this (perhaps using the Jenkins console?).****
>
> ** **
>
> Any insights would be much appreciated.****
>
> ** **
>
> Thanks,****
>
> Bob****
>
>
> *** *** ***
> This message contains information which may be confidential and
> privileged. Unless you are the addressee (or authorized to receive for the
> addressee), you may not use, copy or disclose to anyone the message or any
> information contained in the message. If you have received the message in
> error,  please advise the sender by reply e-mail and delete the message.
>
> --
> 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.
>
>
>

-- 
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.


Reply via email to