On Jenkins, Subversion plugin is upgraded from bundled version 1.54 to current (2015/07/15) version 2.5.1 on the installed Plugins page (Http://my.jenkins.server/pluginManager /installed) found in the "Bindings" column, Subversion plugin more "unbind" button and Jenkins bundled plug-ins (such as Subversion Plugin) there is no "uninstall" button on the interface
Click on the picture above "? button, go to the appropriate help screen and translate its contents as follows: The concept of binding plug-ins applies to plugins bundled with Jenkins, such as The Matrix Authorization plugin.
If you do not do anything special, when the Jenkins plugin is upgraded, its bundle will overwrite any plug-ins currently installed in Jenkins_home.
However, when bundled plugins are manually upgraded, Jenkins binds the plugin to a specific version. In the file system, JENKINS will create an empty file called $jenkins_home/plugins/plugin_name.jpi.pinned to indicate the binding. During Jenkins startup, the binding plug-in will never be overwritten by a bundled plug-in. (If a binding plug-in version is lower than the bundled plug-in version, the new version of Jenkins will be warned.) ）
It is safe to update a bundled plugin to the version provided by the Update center through the plug-in Update center. It is often necessary to pick up the latest features and fixes. The bundled version is occasionally updated, but not fixed.
The plugin management of Jenkins allows the plugin to be displayed to unbind. $JENKINS _home/plugins/plugin_name.jpi.pinned files can also be manually created or deleted to control binding behavior. If it exists, Jenkins will use any version specified by the user, and if not, Jenkins will restore the default plug-in version at startup.
In the case of Subversion plugin, $JENKINS files or directories associated with the _home/plugins/directory, such as:
$JENKINS _home/plugins/subversion.jpi.pinned indicates that subversion plugin is currently bound.
Subversion.bak is the last installed version, SUBVERSION.JPI is the version that is currently in use. Click the "Unbind" button and Jenkins will delete the $jenkins_home/plugins/subversion.jpi.pinned file, and the version of the Subversion plugin will be restored during the Jenkins restart.
Take Docker Commons plugin as an example, create an empty file docker-commons.jpi.pinned under $jenkins_home/plugins/and restart JENKINS.
$JENKINS _home/plugins/docker-commons.jpi.pinned indicates that the Docker Commons plugin is currently bound.
Click the "Unbind" button and JENKINS will erase the $jenkins_home/plugins/subversion.jpi.pinned file.
Note: The bundled plugin for Jenkins is in the Web-inf/plugins directory in Jenkins.war.
Reference: Https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins
Jenkins Pinned Plugins (Jenkins binding plugin)
