Hi Paul, I always have to update of plugins manually as our build servers are separated from the network that has internet access. So I can't tell you much about the update centers functionality atm.
I add the version number to the filename when I update. This way I get a better overview as we store the Jenkins servers configuration, plugins etc. into svn. As Manuel mentioned do some plugins come along with Jenkins which counteracts my approach as I then have to plugins with different versions active at the same time. I wasn't aware that the translation plugin is incorporated to Jenkins. In cases like yours I create an empty file with the same name as the plugins_filename.hpi/jpi and appended a .disabled plus the .pinned file e.g. cvs.hpi.disabled and cvs.hpi.pinned. .pinned files do not disable the shipped plugins. That's at least my experience. Concurring plugins ain't no fun ;) Then I copy the new plugin with the version in the filename into the plugin folder and delete the according subfolder in plugins to be on the safe side. This has always worked fine until now. Hope this help. Jan On 23 Mrz., 12:34, Paul Schwann <paul.schw...@gmail.com> wrote: > Dear Manuel, > > thanks for your message! I've checked the Plugin Manager and indeed the > table shown in the "Installed" tab has a column "Pinned". I read about it > in the Jenkins help and it turns out that this is what you referring to. > None of the plugins (including the "Translation Assistance Plugn") actually > is pinned, though. I created - as described in the help - a file > [jenkins]plugins\translation.hpi.pinned. And yes, now that Plugin > Manager/Installed tabled shows the "unpin" button for the "Translation > Assistance Plugin" (so I assume it is pinned now). Clicking it doesn't do > much but removing the file I've created before and the unpin button is gone > > Apparently, updating any of the plug-ins delivered with the package doesn't > work for me. :-( > > Now let's try to install a new plug-in: > I go to "Available" tab and select ... mmhh ... "Static Code Analysis > Plug-ins". Download, install, restart -> OK After restarting, no new > plugin. [jenkins]\plugin folder doesn't contain any new hpi. > > Let's try it manually. URL of that plugin > ishttp://updates.jenkins-ci.org/download/plugins/analysis-core/1.38/ana... > After uploading, [jenkins]\plugins has a new file analysis-core.jpi. Good. > Now restart Jenkins: et voila, we have a new plugin "Static Analysis > Utilities". > > So the overall mechanism seems to work even if it doesn't directly from the > web interface. Could live with that. > > I really wonder how to update the default plugins as Jenkins overwrites > them all the time during startup... > > Regards, > Paul > > > > > > > >
