Re: Anything wrong with storing expanded plugin data in var cache?

Hello, As a Jenkins User, I've run instances in production or punctually (workshops) with the "plugins" directory into a RAMDISK without issues. When the persistence was required, I use to migrate this to a "machine local directory" (generally hypervisor local disk) to avoid having it stored

Re: Anything wrong with storing expanded plugin data in var cache?

I think it's a genuinely great proposal and it sounds like most of the things I'd be concerned about have already been thoroughly considered and addressed effectively. There are two remaining points to consider: I think it might be desirable to give plugins some mechanism to interact with the

Re: Anything wrong with storing expanded plugin data in var cache?

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 wrote: > I normally store expanded plugin metadata within > /var/cache/jenkins/plugins similar to how WAR filre metadata is

Re: Anything wrong with storing expanded plugin data in var cache?

For context, I asked Sam to come and discuss this here after his comment on the JEP about Essentials Evergreen snapshotting system, in the part where we explain how we plan to aggressively

Anything wrong with storing expanded plugin data in var cache?

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