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 .hp
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 wrote:
> Hi,
>
> I have been having quite a bit of trouble manually inst
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 plu
