blocks|key|2789913|text|我想这是因为Jenkins+forked+from+Hudson，所以它是hpi中的'H‘。J显然是这一点的变化。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2789914|在技术方面，jpi插件是使用gradle+plugin+architecture生成的，hpi插件是使用Maven+architecture生成的。|2789915|最终，正如您所发现的那样，这两者都产生了Jenkins可以使用的插件。绝大多数都是使用Maven构建的，但我是Gradle的粉丝，因为它可以很好地与Groovy中的开发插件相关联。您还可以使用Maven在Groovy中进行构建|2789916|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Jenkins_%2528software%2529|1|https://wiki.jenkins-ci.org/display/JENKINS/Gradle%2BJPI%2BPlugin|2|https://wiki.jenkins-ci.org/display/JENKINS/Plugin%2Btutorial#Plugintutorial-CreatingaNewPlugin^0|6|Q|0|0|E|Q|1|1G|I|2|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|D|3|E|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]|$A|11|B|12|1|13]]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]|R|$5|K|L|M|C|$N|S]]]]

Well I think its because <a href="http://en.wikipedia.org/wiki/Jenkins_%28software%29">Jenkins forked from Hudson</a> so that is the 'H' in hpi. The J is obviously a change to that.

In terms of technology, the jpi plugins are generated using the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Gradle+JPI+Plugin">gradle plugin architecture</a> and hpi plugins are generated with the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-CreatingaNewPlugin">Maven architecture</a>

Ultimately, as you have found both produce plugins which Jenkins can use. The vast majority are built using Maven but I am a fan of Gradle as it links nicely in with developing plugins in Groovy. You can also build in Groovy using Maven

blocks|key|5107713|text|两者都应该与Jenkins在手动安装时将hpi重命名为jpi的扩展完全相同。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5107714|您在JENKINS_HOME中同时看到这两个插件的原因是Jenkins启动时加载插件的顺序:如果这两个插件都存在，则plugin.jpi优先于plugin.hpi。这是上载安装确保在重启后上载的版本将覆盖现有版本的方式。|5107715|entityMap^0|K|3|R|3|0|1M|A|1Z|A|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

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

The reason why you see both in your JENKINS_HOME is the order in which plugins are loaded when Jenkins boots up: <code>plugin.jpi</code> gets precedence over <code>plugin.hpi</code> 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.

blocks|key|2789979|text|$JENKINS_HOME/plugins/中的插件应该始终使用.jpi后缀(基名是插件标识符)。通常情况下，Jenkins会强制使用这种命名模式，即使在uploading+a+plugin+manually时也是如此，无论您在上传时使用了什么文件名，所以我不确定您是如何在这里获得*.hpi文件的，除非您直接将其复制到此文件系统位置。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2789980|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jenkinsci/jenkins/blob/8d73038a27420fdee0f5b4f97b47229c243345e8/core/src/main/java/hudson/model/UpdateCenter.java#L1957^0|0|M|W|4|3X|5|25|R|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

Plugins as present in <code>$JENKINS_HOME/plugins/</code> should always be using the <code>.jpi</code> suffix (with the basename being the plugin identifier). Normally Jenkins will enforce this naming pattern even when <a href="https://github.com/jenkinsci/jenkins/blob/8d73038a27420fdee0f5b4f97b47229c243345e8/core/src/main/java/hudson/model/UpdateCenter.java#L1957" rel="nofollow noreferrer">uploading a plugin manually</a>, regardless of what filename you used for the upload, so I am not sure how you came to have a <code>*.hpi</code> file here, unless you directly copied it into this filesystem location.

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

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

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

What is difference between .hpi and .jpi of Jenkins plugins?

33 天实现自己的 AI 进化论？发文瓜分机械键盘、耳机等万元奖池！点击参加活动：<a href="https://cloud.tencent.com/developer/article/2503022" target="_blank">https://cloud.tencent.com/developer/article/2503022</a> 
 <img src="https://qcloudimg.tencent-cloud.cn/raw/01543e0407db10898a7ee9f420794432.jpg"/>

技术创作特训营有奖征文

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云AI代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

文章&问答评论现已支持表情

我已经通过两种方式安装了Jenkins插件，一种是手动将.hpi文件保存在Jenkins主目录中，另一种是从Jenkins前端安装(管理Jenkins >管理插件)。我在这里注意到的是，当我手动安装插件(下载为.hpi文件)时，它安装了扩展名为.hpi的插件，而通过Jenkins前端安装插件时，我注意到插件再次安装为....

问Jenkins插件的.hpi和.jpi有什么不同？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Jenkins插件的.hpi和.jpi有什么不同？EN