That could pose a problem, yes... File list is indeed /var/lib/jenkins/plugins/*.jpi. One way of doing it is have the initial provisioning with Puppet with the package listed as 'installed', but let the user update those plugins afterwards through UpdateCenter.
On Tuesday, December 4, 2012 8:31:41 PM UTC+1, Jesse Glick wrote: > > On 12/04/2012 02:10 PM, Dieter De Meyer wrote: > > we fetch the list of latest plugins from updates.jenkins-ci.org and for > each plugin we create an RPM package > > What is the file list, i.e. where you do place plugins so as to ensure > that Jenkins loads them automatically? /var/lib/jenkins/plugins/*.jpi would > I suppose work > initially but the package manager would get confused if you updated one of > these plugins from within Jenkins itself. >
