Hello, I'm trying to devise a process where all Jenkins plugins get upgraded through a script and I've noticed that bundled plugins (e.g. mailer) get downgraded back to their original versions after Jenkins is restarted.
1. Install fresh instance of Jenkins 2. Download newer plugins into ~/plugins (e.g. http://updates.jenkins-ci.org/latest/mailer.hpi) 3. Restart Jenkins Result: mailer.jpi gets reverted to original version The only way to make the newer version "stick" appears to be the creation of a *.pinned file. 1. Install fresh instance of Jenkins 2. Download newer plugins into ~/plugins (e.g. http://updates.jenkins-ci.org/latest/mailer.hpi) 3. Create the .pinned file (e.g. mailer.pinned) 4. Restart Jenkins Result: newer/pinned version is deployed. Is there a way to make Jenkins accept the newer plugins and not try to deploy the bundled versions? Furthermore, does the fact that bundled plugins get redeployed mean that their version have some significance? Is it a best practice to use, say, Jenkins 1.630 with the bundled Mailer 1.11 plugin (and not the latest 1.15 version)? Giovanni -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ad2523af-bca4-4e98-a060-5c10a5c42d38%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
