[ https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161804#comment-161804 ]
SCM/JIRA link daemon commented on JENKINS-13129: ------------------------------------------------ Code changed in jenkins User: Alex Lehmann Path: core/src/main/java/hudson/PluginManager.java test/src/test/java/hudson/PluginManagerTest2.java http://jenkins-ci.org/commit/jenkins/2453985ca5f4cb2c824466d132fe3658020b72fe Log: [Fixed JENKINS-13129] Updating built-in plugins doesn't work, the file doesn't get pinned and is overwritten on the next startup changed bundled plugin detection, added unit test > Updating built-in plugins doesn't work, the file doesn't get pinned and is > overwritten on the next startup > ---------------------------------------------------------------------------------------------------------- > > Key: JENKINS-13129 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13129 > Project: Jenkins > Issue Type: Bug > Components: core > Affects Versions: current > Environment: jenkins 1.456, tomcat 7.0.25, java 1.6.0-31 running on > windows vista > Reporter: Alex Lehmann > Assignee: Alex Lehmann > Priority: Critical > > I still cannot update cvs or subversion plugins without manually creating a > .pinned file. > When e.g. updating cvs plugin 1.6 (shipped with jenkins.war) to 2.1, the file > is installed into the plugin dir, but no cvs.jpi.pinned file is created. When > restarting the tomcat server, the file is replaced by the 1.6 version from > the war directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira