[ 
https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158920#comment-158920
 ] 

Alex Lehmann edited comment on JENKINS-12583 at 2/12/12 2:53 PM:
-----------------------------------------------------------------

I had to set up a "fresh" jenkins instance (1.450) for dev testing, so I had a 
new chance to check if updating the plugins works or not, it turns out it 
doesn't.

This is not a cvs isuse, however, the subversion plugin doesn't update as well. 
The file is updated in the plugin directory, but the .pinned file is not 
created so that old plugin is reinstalled when restarting the server.

When I create the .pinned files manually after shutting down the server, the 
update works, that provides a work-around at least.

The issue for the general problem is JENKINS-12514, I think this issue relating 
to cvs can be closed.


                
      was (Author: alexlehm):
    I had to set up a "fresh" jenkins instance for dev testing, so I had a new 
chance to check if updating the plugins works or not, it turns out it doesn't.

This is not a cvs isuse, however, the subversion plugin doesn't update as well. 
The file is updated in the plugin directory, but the .pinned file is not 
created so that old plugin is reinstalled when restarting the server.

I will open a new issue for general plugins, unless there is one already, I 
think this issue relating to cvs can be closed.


                  
> update for cvs plugin to 2.0 doesn't work
> -----------------------------------------
>
>                 Key: JENKINS-12583
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12583
>             Project: Jenkins
>          Issue Type: Bug
>          Components: cvs
>    Affects Versions: current
>         Environment: jenkins 1.449, cvs plugin 1.6
>            Reporter: Alex Lehmann
>             Fix For: current
>
>
> I tried to update to the cvs plugin 2.0 today but this doesn't work, I assume 
> there is a name problem due to the extension *.jpi on the new plugin.
> Before update, the file is called cvs.hpi, the update process creates a new 
> file cvs.jpi that is ignored with the following message:
> Jan 30, 2012 5:04:26 PM hudson.PluginManager$1$3$1 isDuplicate
> INFO: Ignoring /home/lehmann/.jenkins/plugins/cvs.jpi because 
> /home/lehmann/.jenkins/plugins/cvs.hpi is already loaded
> I assume it may work if it were the other way around.
> The version displayed by the plugin page remains 1.6 but there are a few 
> exceptions in the log about missing classes like this
> java.lang.NoClassDefFoundError: org/netbeans/lib/cvsclient/admin/AdminHandler
> these classes are included in the cvs.jpi zip but that is not used.
> I was able to fix the update manually by copying cvs.jpi to cvs.hpi, which 
> resulted in a pinned plugin 2.0, but the automatic process has to be fixed 
> somehow.

--
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

        

Reply via email to