The slightly longer answer is that there is code in Jenkins to migrate the files to the new extension, but it can get confused so safest is to follow what your Jenkins looks to be doing so that you don't keep re-invoking the migration code (which is designed to run once, but each time you put a .hpi file in there it runs again)
Uploading via the browser side-steps the whole shebang! On 9 May 2013 16:59, Stephen Connolly <stephen.alan.conno...@gmail.com>wrote: > If your $JENKINS_HOME/plugins has files called .jpi then RENAME the .hpi > files to .jpi *before* copying them into $JENKINS_HOME/plugins > > IOW use the naming convention that your Jenkins is using. > > > On 7 May 2013 20:03, Tony P <tony...@cantabrian.co.nz> wrote: > >> Hi, >> >> I have been having quite a bit of trouble manually installing plugin >> updates and would like to pose a theory. I have a system behind firewalls >> without internet access, it was originally created in a different >> environment WITH internet access and copied here. >> >> When I download the latest plugins and copy them to Jenkins and *restart*a >> number fail to start with errors like: >> >> May 07, 2013 3:42:56 PM hudson.PluginManager$1$3$1 isDuplicate >> INFO: Ignoring D:\Jenkins\plugins\cobertura.hpi because >> D:\Jenkins\plugins\cobertura.jpi is already loaded >> >> I have read that when you download via the Internet the files are >> "my-plugin*.jpi*" but if I download them then it's "my-plugin*.hpi*" - I >> am downloading from http://updates.jenkins-ci.org/download/plugins/ >> >> For one failing plugin I deleted the existing active-directory.jpi copied >> over the new active-directory.hpi and voila it worked. >> >> I believe the problem is the inconsistency in the file extension is the >> problem. My sense of it is that people either update one way or the other >> but not both. I am writing up some instructions and would like to get it >> right. I have Googled for Africa but can't find an answer. >> >> Cheers >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
