[
https://issues.jenkins-ci.org/browse/JENKINS-13129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160387#comment-160387
]
sogabe commented on JENKINS-13129:
----------------------------------
JENKINS-12514 will be fixed in 1.456. See http://jenkins-ci.org/changelog.
> 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.457-snapshot, tomcat 7.0.25, java 1.6.0-31
> running on windows vista
> jenkins 1.455, tomcat 7.0.26, java 1.6.0-31 running on ubuntu 11.10
> Reporter: Alex Lehmann
>
> 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 is probably related to JENKINS-12514, but wasn't fixed then
--
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
