I've done this in a rather crude way by looking for the signature of the
plugin in the job's config.xml. If you want to find what to look for in
the config file, you can add the plugin to a job that doesn't have it,
having saved a copy of config.xml before the plugin was added, and
compare with config.xml after the plugin was added. Then you can use
something like "grep -l" to find out which, if any, config files contain
a reference to the plugin. You can do the same thing more elegantly
using Groovy, but the exact code varies depending on which plugin it is.
Regards,
Eric
On 5/29/2013 8:05 PM, jdtangney wrote:
Our Jenkins setup has grown rather um, "organically". We now have lots
of plugins installed and I am sure several are not even used. Worse,
we seem to have cases where two plugins do almost the same thing.
How can I identify which plugins are not used by any existing job? I
want to uninstall them.
Thanks,
--johnt
--
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/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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
