[
https://issues.jenkins-ci.org/browse/JENKINS-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163576#comment-163576
]
dogfood commented on JENKINS-13909:
-----------------------------------
Integrated in !http://ci.jenkins-ci.org/images/16x16/yellow.png!
[jenkins_main_trunk #1740|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1740/]
[JENKINS-13909] don't keep legacy *.hpi when uploading a plugin (Revision
de5938b3a65ea0f33bb0be077decce0b05683cd4)
Result = UNSTABLE
Nicolas De Loof :
[de5938b3a65ea0f33bb0be077decce0b05683cd4|https://github.com/jenkinsci/jenkins/commit/de5938b3a65ea0f33bb0be077decce0b05683cd4]
Files :
* core/src/main/java/hudson/PluginManager.java
> Plugin update via manual upload fails on recent Jenkins version ?
> -----------------------------------------------------------------
>
> Key: JENKINS-13909
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13909
> Project: Jenkins
> Issue Type: Bug
> Components: update-center
> Environment: Jenkins 1.447.1, 1.465
> Reporter: Yama Tksh
>
> Plugin update via manual upload seems to have a problem relating to jpi/hpi
> files.
> Initially, our $JENKINS_HOME/plugins/ folder had the following contents:
> * myplugin.hpi - old version
> * myplugin/ - old version
> Then I uploaded a new version of myplugin.hpi file via web upload function on
> the pluginManager/advanced page,
> and restarted Jenkins.
> 1). On Jenkins 1.424.6, the update succeeded. The plugins/ folder was updated
> as follows:
> * myplugin.hpi - new version (shown version name - OK)
> * myplugin/ - new version - OK
> * (myplugin.bak file was not created)
> 2). On Jenkins 1.447.1, the new version name was correctly shown in the
> plugin list,
> but the update itself failed:
> * myplugin.jpi - new version (shown version name - OK)
> * myplugin.hpi - old version
> * myplugin/ - old version - NG
> 3). On Jenkins 1.465, the update itself succeeded, but the old version name
> was shown:
> * myplugin.jpi - new version
> * myplugin.hpi - old version (shown version name - NG)
> * myplugin/ - new version - OK
> In the cases of 2) and 3),
> when I removed myplugin.hpi and restarted Jenkins,
> then both of the update and shown version name became O.K.
--
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