[JIRA] (JENKINS-12583) update for cvs plugin to 2.0 doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Clarke updated JENKINS-12583: - Component/s: core Since this is a plugin not being picked up, rather than a failure in the plugin, I'm adding this to the core. 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: core, cvs Affects Versions: current Environment: jenkins 1.449, cvs plugin 1.6 Reporter: Alex Lehmann Assignee: 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
[JIRA] (JENKINS-12583) update for cvs plugin to 2.0 doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160270#comment-160270 ] Vince McIntyre commented on JENKINS-12583: -- 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. 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 Assignee: 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
[JIRA] (JENKINS-12583) update for cvs plugin to 2.0 doesn't work
[
https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160271#comment-160271
]
Vince McIntyre commented on JENKINS-12583:
--
A comment. In 1.455 the .war contains references to .hpi files, but the pinning
stuff only works properly with .jpi files.
{code}
% 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
{code}
{code}
% 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
%
{code}
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
Assignee: 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
[JIRA] (JENKINS-12583) update for cvs plugin to 2.0 doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158953#comment-158953 ] jeremyt commented on JENKINS-12583: --- 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. 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 Assignee: 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
[JIRA] (JENKINS-12583) update for cvs plugin to 2.0 doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158805#comment-158805 ] Alex Lehmann commented on JENKINS-12583: 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. 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
[JIRA] (JENKINS-12583) update for cvs plugin to 2.0 doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158802#comment-158802 ] Sergey Bushov commented on JENKINS-12583: - 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. 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
