• Icon: Bug Bug
    • Resolution: Postponed
    • Icon: Major Major
    • core, cvs-plugin
    • None
    • jenkins 1.449, cvs plugin 1.6

      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.

          [JENKINS-12583] update for cvs plugin to 2.0 doesn't work

          karianna added a comment -

          Problem still exists in 1.450, default plugin is now .jpi extension, but upgrade problem remains, even with fresh install.

          karianna added a comment - Problem still exists in 1.450, default plugin is now .jpi extension, but upgrade problem remains, even with fresh install.

          Sergey Bushov added a comment -

          I'm also not able to update from 1.6 to 2.0, and the workaround does not work for me. I don't see the mentioned exceptions/errors in log, but the plugin stays on version 1.6 after update.

          Sergey Bushov added a comment - I'm also not able to update from 1.6 to 2.0, and the workaround does not work for me. I don't see the mentioned exceptions/errors in log, but the plugin stays on version 1.6 after update.

          Alex Lehmann added a comment -

          Are you sure that you have the plugin pinnned?

          I have the following files in the jenkins/plugins dir:

          cvs
          cvs.jpi
          cvs.jpi.pinned

          if that is the case, the main jenkins should update the plugin to the old version anymore

          in 1.450 it is supposed to be fixed, but I haven't tried that yet.

          Alex Lehmann added a comment - Are you sure that you have the plugin pinnned? I have the following files in the jenkins/plugins dir: cvs cvs.jpi cvs.jpi.pinned if that is the case, the main jenkins should update the plugin to the old version anymore in 1.450 it is supposed to be fixed, but I haven't tried that yet.

          Alex Lehmann added a comment - - edited

          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.

          Alex Lehmann added a comment - - edited 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.

          Alex Lehmann added a comment -

          waiting for the general plugin fix

          Alex Lehmann added a comment - waiting for the general plugin fix

          jeremyt added a comment -

          This may help someone...
          I cannot comment on whether the CVS plugin works or not, but I upgraded from v1.6 to v2.0 at the same time as upgrading Jenkins from 1.448 to 1.450 and I 'lost' a couple of Jobs (all source in a SVN repo, nothing in CVS).

          Down-graded the CVS plugin from 2.0 to 1.6 and the Jobs returned.

          jeremyt added a comment - This may help someone... I cannot comment on whether the CVS plugin works or not, but I upgraded from v1.6 to v2.0 at the same time as upgrading Jenkins from 1.448 to 1.450 and I 'lost' a couple of Jobs (all source in a SVN repo, nothing in CVS). Down-graded the CVS plugin from 2.0 to 1.6 and the Jobs returned.

          Still seeing this on a fresh install of 1.454, and after upgrade to 1.455.
          The workaround of touching the .hpi for bundled plugins still works.

          Vince McIntyre added a comment - Still seeing this on a fresh install of 1.454, and after upgrade to 1.455. The workaround of touching the .hpi for bundled plugins still works.

          Vince McIntyre added a comment - - edited

          A comment. In 1.455 (installed via the .deb package) the .war contains references to .hpi files, but the pinning stuff only works properly with .jpi files.

          % unzip -l /usr/share/jenkins/jenkins.war|grep hpi|awk '{print $NF}'
          WEB-INF/plugins/ssh-slaves.hpi
          WEB-INF/plugins/javadoc.hpi
          WEB-INF/plugins/cvs.hpi
          WEB-INF/plugins/translation.hpi
          WEB-INF/plugins/ant.hpi
          WEB-INF/plugins/maven-plugin.hpi
          WEB-INF/plugins/subversion.hpi
          
          % find /var/lib/jenkins/ -name "*.hpi*"
          %
          % find /var/lib/jenkins/ -name "*.pinn*"
          /var/lib/jenkins/plugins/cvs.jpi.pinned
          /var/lib/jenkins/plugins/subversion.jpi.pinned
          %
          

          Vince McIntyre added a comment - - edited A comment. In 1.455 (installed via the .deb package) the .war contains references to .hpi files, but the pinning stuff only works properly with .jpi files. % unzip -l /usr/share/jenkins/jenkins.war|grep hpi|awk '{print $NF}' WEB-INF/plugins/ssh-slaves.hpi WEB-INF/plugins/javadoc.hpi WEB-INF/plugins/cvs.hpi WEB-INF/plugins/translation.hpi WEB-INF/plugins/ant.hpi WEB-INF/plugins/maven-plugin.hpi WEB-INF/plugins/subversion.hpi % find / var /lib/jenkins/ -name "*.hpi*" % % find / var /lib/jenkins/ -name "*.pinn*" / var /lib/jenkins/plugins/cvs.jpi.pinned / var /lib/jenkins/plugins/subversion.jpi.pinned %

          Since this is a plugin not being picked up, rather than a failure in the plugin, I'm adding this to the core.

          Michael Clarke added a comment - Since this is a plugin not being picked up, rather than a failure in the plugin, I'm adding this to the core.

          Alex Lehmann added a comment -

          fixed with JENKINS-13129

          Alex Lehmann added a comment - fixed with JENKINS-13129

            alexlehm Alex Lehmann
            alexlehm Alex Lehmann
            Votes:
            3 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: