Jenkins插件的.hpi和.jpi有什么区别? [英] What is difference between .hpi and .jpi of Jenkins plugins?

查看:1353
本文介绍了Jenkins插件的.hpi和.jpi有什么区别?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经通过两种方式安装了Jenkins插件,即手动将.hpi文件保存在Jenkins主目录中,然后从Jenkins前端安装(管理Jenkins>管理插件).

I have installed Jenkins plugins in two ways i.e. manually keeping the .hpi file in Jenkins home directory, and installing from Jenkins front-end (Manage Jenkins > Manage Plugins).

我在这里注意到的是,当我手动安装插件(下载为.hpi文件)时,它以扩展名.hpi安装,并且在通过Jenkins前端安装插件时,我注意到该插件再次安装为.jpi.

What I notice here is when I install the plugin manually (downloaded as .hpi file) it installed with extension .hpi and while installing the plugin through Jenkins front-end I notice that plugin again installed as .jpi.

但是为什么呢?后台发生了什么事?我知道功能不会改变,但是它看起来很有趣.

But why? What is going on in the background? I know functionality won't change but it looks interesting to know.

推荐答案

这两个假设都与Jenkins按您说的手动安装将hpi重命名为jpi的扩展名相同.

Both are supposed to be identical to that extend that Jenkins is renaming hpi to jpi when you install it manually as you said.

在JENKINS_HOME中看到两者的原因是Jenkins引导时加载插件的顺序:plugin.jpi优先于plugin.hpi(如果两者都存在).通过这种方式,上载安装可确保重新启动后上载的版本将覆盖现有版本.

The reason why you see both in your JENKINS_HOME is the order in which plugins are loaded when Jenkins boots up: plugin.jpi gets precedence over plugin.hpi in case both are present. This is the way the upload installation makes sure the uploaded version will override the existing one after the restart.

这篇关于Jenkins插件的.hpi和.jpi有什么区别?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆