I see nothing wrong with it... but I would say that having added the --pluginroot option myself iirc ;-)
On 24 March 2018 at 00:29, Sam Gleske <[email protected]> wrote: > I normally store expanded plugin metadata within > /var/cache/jenkins/plugins similar to how WAR filre metadata is stored in > /var/cache/jenkins/war. > > Is there any particular reason the Jenkins packages don't do this? Are > there any drawbacks? I'm curious if others have any opinions on this. > > I've been running Jenkins quite a while like this. > > [1]: https://github.com/samrocketman/jenkins-bootstrap-shared/blob/ > 1a409cad89007f56ed36342427b767dd4e88fbd9/packaging/docker/run.sh.in#L38 > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" 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-dev/05beb1e5-a824-428c-b980-07a4e343acdc% > 40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/CA%2BnPnMw%2BeDUdC4eGaBDk9k4dA6t7FHhFQv2-%2B8N14SBQZMFzuA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
