blocks|key|199702|text|可以，停那儿吧。下载插件(*.hpi文件)并将其放入以下目录：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|199703|<jenkinsHome>/plugins/|code-block|syntax|javascript|199704|之后，您将需要重新启动Jenkins。|199705|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Yes, you can. Download the plugin (*.hpi file) and put it in the following directory:

<pre><code>&lt;jenkinsHome&gt;/plugins/
</code></pre>

Afterwards you will need to restart Jenkins.

blocks|key|197161|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|197162|下载插件。|ordered-list-item|197163|Inside+Jenkins:+Manage+Jenkins→Manage+Plugins→有一个名为高级的选项卡，在该页面上有一个上载插件的选项(文件的扩展名必须是hpi)。|197164|197165|有时，当您下载插件时，您可能会得到(.zip)文件，然后只需使用(.hpi)重命名，然后使用UI安装插件。|197166|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|K|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|L|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|M|7|@]|8|@]|9|$]]|$1|F|3|-4|4|5|6|N|7|@]|8|@]|9|$]]|$1|G|3|H|4|5|6|O|7|@]|8|@]|9|$]]|$1|I|3|-4|4|5|6|P|7|@]|8|@]|9|$]]]|J|$]]

<ol>
<li>Download the plugin.</li>
<li>Inside Jenkins: Manage Jenkins → Manage Plugins → There is a tab called Advanced and on that page there is an option to upload a plugin (the extension of the file must be hpi).</li>
</ol>

Sometimes, when you download plugins you may get (.zip) files then just rename with (.hpi) and use the UI to install the plugin.

blocks|key|3038051|text|如果你使用Docker，你应该阅读这个文件：https://github.com/cloudbees/jenkins-ci.org-docker/blob/master/plugins.sh|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3038052|父Dockerfile示例：|3038053|FROM+jenkins
COPY+plugins.txt+/plugins.txt
RUN+/usr/local/bin/plugins.sh+/plugins.txt|code-block|syntax|javascript|3038054|plugins.txt|3038055|<name>:<version>
<name2>:<version2>|3038056|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/cloudbees/jenkins-ci.org-docker/blob/master/plugins.sh^0|M|21|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|C|$I|J]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

If you use Docker, you should read this file: <a href="https://github.com/cloudbees/jenkins-ci.org-docker/blob/master/plugins.sh" rel="noreferrer">https://github.com/cloudbees/jenkins-ci.org-docker/blob/master/plugins.sh</a>

Example of a parent Dockerfile:

<pre><code>FROM jenkins
COPY plugins.txt /plugins.txt
RUN /usr/local/bin/plugins.sh /plugins.txt
</code></pre>

plugins.txt

<pre><code>&lt;name&gt;:&lt;version&gt;
&lt;name2&gt;:&lt;version2&gt;
</code></pre>

blocks|key|3038024|text|我已经创建了一个执行以下操作的简单脚本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3038025|3038026|将一个或多个插件下载到插件目录|unordered-list-item|3038027|扫描该目录中的所有插件以查找缺少的依赖项以及|3038028|循环，直到没有任何打开的依赖项存在为止|3038029|3038030|该脚本不需要运行jenkins+-我使用它来配置docker+box。|3038031|https://gist.github.com/micw/e80d739c6099078ce0f3|offset|length|3038032|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|0|1D|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|Z|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|10|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|11|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|12|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|14|8|@]|9|@$O|15|P|16|1|17]]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|N]]]]

I have created a simple script that does the following:

<ul>
<li>Download one or more plugins to the plugin directory</li>
<li>Scan all plugins in that directory for missing dependencies</li>
<li>download this dependencies as well</li>
<li>loop until no open dependencies are left</li>
</ul>

The script requires no running jenkins - I use it to provision a docker box.

<a href="https://gist.github.com/micw/e80d739c6099078ce0f3">https://gist.github.com/micw/e80d739c6099078ce0f3</a>

blocks|key|197840|text|有时，当您下载插件时，您可能会得到(.zip)文件，然后只需使用(.hpi)重命名，然后提取所有插件并移动到<jenkinsHome>/plugins/目录。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|197841|entityMap^0|1I|M|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Sometimes when you download plugins you may get (.zip) files then just rename with (.hpi) and then extract all the plugins and move to <code>&lt;jenkinsHome&gt;/plugins/</code> directory.

blocks|key|199808|text|Docker更新:使用install-plugins.sh脚本。它采用一个不带'-+plugin‘扩展名的插件名称列表。请参阅说明here。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|199809|install-plugins.sh取代了过时的plugins.sh，它现在会发出警告：|199810|WARN:+plugins.sh+is+deprecated,+please+switch+to+install-plugins.sh|style|CODE|199811|要按照plugins.sh使用plugins.txt，请参阅this+issue和此解决方法：|199812|RUN+/usr/local/bin/install-plugins.sh+$(cat+/usr/share/jenkins/plugins.txt+%7C+tr+'\n'+'+')|199813|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/jenkinsci/docker/blob/master/install-plugins.sh|1|https://github.com/jenkinsci/docker/blob/master/README.md#preinstalling-plugins|2|https://github.com/jenkinsci/docker/issues/348^0|B|I|0|1T|4|1|0|0|0|1V|0|U|A|2|0|0|2H|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]|$A|13|B|14|1|15]]|C|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|17|8|@$A|18|B|19|H|I]]|9|@]|C|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|L|3|M|5|6|7|1E|8|@$A|1F|B|1G|H|I]]|9|@]|C|$]]|$1|N|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]|V|$5|Q|R|S|C|$T|W]]|X|$5|Q|R|S|C|$T|Y]]]]

Update for Docker: use the <a href="https://github.com/jenkinsci/docker/blob/master/install-plugins.sh" rel="noreferrer">install-plugins.sh</a> script. It takes a list of plugin names minus the '-plugin' extension. See the description <a href="https://github.com/jenkinsci/docker/blob/master/README.md#preinstalling-plugins" rel="noreferrer">here</a>.

install-plugins.sh replaces the deprecated plugins.sh which now warns :

<code>WARN: plugins.sh is deprecated, please switch to install-plugins.sh</code>

To use a plugins.txt as per plugins.sh see <a href="https://github.com/jenkinsci/docker/issues/348" rel="noreferrer">this issue</a> and this workaround:

<code>RUN /usr/local/bin/install-plugins.sh $(cat /usr/share/jenkins/plugins.txt | tr '\n' ' ')</code>

blocks|key|2825325|text|使用https://updates.jenkins-ci.org/download/plugins/。从Jenkins的这个中央更新库下载它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2825326|entityMap|0|LINK|mutability|MUTABLE|url|https://updates.jenkins-ci.org/download/plugins/^0|2|1C|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Use <a href="https://updates.jenkins-ci.org/download/plugins/" rel="noreferrer">https://updates.jenkins-ci.org/download/plugins/</a>. Download it from this central update repository for Jenkins.

blocks|key|197200|text|公认的答案是正确的，但请确保还安装了所有必要的依赖项。使用命令行界面或web安装似乎可以解决这个问题，但直到我安装了依赖项，我的插件才会显示在浏览器中或使用java+-jar+jenkins-cli.jar+-s+http://localhost:8080+list-plugins。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|197201|entityMap^0|26|1R|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

The accepted answer is accurate, but make sure that you also install all necessary dependencies as well. Installing using the CLI or web seems to take care of this, but my plugins were not showing up in the browser or using <code>java -jar jenkins-cli.jar -s http://localhost:8080 list-plugins</code> until I also installed the dependencies.

blocks|key|3038121|text|给出的答案是有效的，并添加了插件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3038122|如果你想替换/更新一个内置的插件，比如credentials插件，它有依赖关系，那么你必须使用前端。为了实现自动化，我使用：|3038123|+curl+-i+-F+file=@pluginfilename.hpi+http://jenkinshost/jenkins/pluginManager/uploadPlugin|code-block|syntax|javascript|3038124|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The answers given work, with added plugins.

If you want to replace/update a built-in plugin like the credentials plugin, that has dependencies, then you have to use the frontend. To automate I use:

<pre><code> curl -i -F file=@pluginfilename.hpi http://jenkinshost/jenkins/pluginManager/uploadPlugin
</code></pre>

blocks|key|3038230|text|在我的例子中，我需要在运行Windows+server的离线构建服务器上安装一个插件(版本在这里不重要)。我已经在我的笔记本电脑上安装了Jenkins，以便提前测试更改，它在localhost:8080上作为一项windows服务运行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3038231|因此，如果你愿意花时间在一台有互联网连接的机器上设置Jenkins，并将这些更改带到离线服务器Jenkins+(它是有效的，我确认了！)，以下是你可以遵循的步骤：|3038232|在我的笔记本电脑上打开Jenkins，http://localhost:8080|offset|length|3038233|Navigator:+Manage+Jenkins+%7C+Download+plugin+|unordered-list-item|3038234|
+install选项|3038235|Windows+Explorer:复制下载的插件文件，该文件位于"c:\program+files+(x86)\+Jenkins+\plugins“文件夹(即，将其复制到脱机服务器中的共享文件夹中)|3038236|
|3038237|StopJenkins+Service+(Offline+|3038238|+Jenkins)+|3038239|+Component+Services，Jenkins+Service+server|3038240|Restart+Jenkins将插件文件(即role-strategy.jpi+y.jpi)复制到(Offline+Jenkins)+|3038241|Jenkins上的"c:\program+files+(X86)\Jenkins\|3038242|“文件夹中，瞧！应该安装它。|3038243|3038244|3038245|entityMap|0|LINK|mutability|MUTABLE|url|http://localhost:8080/^0|0|0|J|L|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1E|8|@]|9|@$F|1F|G|1G|1|1H]]|A|$]]|$1|H|3|I|5|J|7|1I|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1J|8|@]|9|@]|A|$]]|$1|M|3|N|5|J|7|1K|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Q|3|R|5|J|7|1M|8|@]|9|@]|A|$]]|$1|S|3|T|5|J|7|1N|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|X|5|J|7|1P|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|10|3|11|5|J|7|1R|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1U|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]]]

In my case, I needed to install a plugin to an offline build server that's running a Windows Server (version won't matter here). I already installed Jenkins on my laptop to test out changes in advance and it is running on localhost:8080 as a windows service.

So if you are willing to take the time to setup Jenkins on a machine with Internet connection and carry these changes to the offline server Jenkins (it works, confirmed by me!), these are steps you could follow:

<ul>
<li>Jenkins on my laptop: Open up Jenkins, <a href="http://localhost:8080" rel="nofollow noreferrer">http://localhost:8080</a></li>
<li>Navigator: Manage Jenkins | Download plugin without install option</li>
<li>Windows Explorer: Copy the downloaded plugin file that is located at "c:\program files (x86)\Jenkins\plugins" folder (i.e. role-strategy.jpi)</li>
<li>Paste it into a shared folder in the offline server</li>
<li>Stop the Jenkins Service (Offline Server Jenkins) through Component Services, Jenkins Service</li>
<li>Copy the plugin file (i.e. role-strategy.jpi) into "c:\program files (x86)\Jenkins\plugins" folder on the (Offline Jenkins) server</li>
<li>Restart Jenkins and voila! It should be installed. </li>
</ul>

blocks|key|197964|text|这是一种将插件从一个Jenkins+box复制到另一个的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|197965|复制插件目录：|197966|scp+-r+jenkins-box.url.com:/var/lib/jenkins/plugins+.|code-block|syntax|javascript|197967|压缩插件：|197968|tar+cvfJ+plugins.tar.xz+plugins|197969|将它们复制到其他Jenkins框中：|197970|scp+plugins.tar.xz+different-jenkins-box.url.com
ssh+different-jenkins-box.url.com+"tar+xvfJ+plugins.tar.xz+-C+/var/lib/jenkins"|197971|重新启动Jenkins。|197972|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|Z|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|11|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

This is a way to copy plugins from one Jenkins box to another.

Copy over the plugins directory:

<pre><code>scp -r jenkins-box.url.com:/var/lib/jenkins/plugins .
</code></pre>

Compress the plugins:

<pre><code>tar cvfJ plugins.tar.xz plugins
</code></pre>

Copy them over to the other Jenkins box:

<pre><code>scp plugins.tar.xz different-jenkins-box.url.com
ssh different-jenkins-box.url.com "tar xvfJ plugins.tar.xz -C /var/lib/jenkins"
</code></pre>

Restart Jenkins.

blocks|key|197926|text|要安装插件"git“及其所有依赖项：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|197927|curl+-XPOST+http://localhost:8080/pluginManager/installNecessaryPlugins+-d+'<install+plugin="git@current"+/>'|code-block|syntax|javascript|197928|在这里，安装的插件是git；Jenkins会忽略指定为@current的版本。Jenkins在localhost端口8080上运行，请根据需要更改此端口。据我所知，这是‘手动’安装一个插件及其所有依赖项的最简单方法。在Jenkins+v1.644上测试|offset|length|style|CODE|197929|entityMap^0|0|0|A|3|R|8|1B|9|1M|4|39|6|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@$I|R|J|S|K|L]|$I|T|J|U|K|L]|$I|V|J|W|K|L]|$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$]]

To install plugin "git" with all its dependencies:

<pre><code>curl -XPOST http://localhost:8080/pluginManager/installNecessaryPlugins -d '&lt;install plugin="git@current" /&gt;'
</code></pre>

Here, the plugin installed is <code>git</code> ; the version, specified as <code>@current</code> is ignored by Jenkins. Jenkins is running on <code>localhost</code> port <code>8080</code>, change this as needed. As far as I know, this is the simplest way to install a plugin with all its dependencies 'by hand'. Tested on Jenkins <code>v1.644</code>

blocks|key|2825363|text|RUN+/usr/local/bin/install-plugins.sh+amazon-ecs:1.37+configuration-as-code:1.47+workflow-aggregator:2.6+\
cloudbees-folder:6.15+antisamy-markup-formatter:2.1+build-timeout:1.20+credentials-binding:1.24+|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|2825364|猫出plugins.txt并安装在Dockerfile中，如上所述。|unstyled|2825365|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>RUN /usr/local/bin/install-plugins.sh amazon-ecs:1.37 configuration-as-code:1.47 workflow-aggregator:2.6 \
cloudbees-folder:6.15 antisamy-markup-formatter:2.1 build-timeout:1.20 credentials-binding:1.24 
</code></pre>
Cat out the plugins.txt and install in Dockerfile as above.

blocks|key|3038272|text|使用此链接下载插件的hpi的最新版本。https://updates.jenkins-ci.org/download/plugins/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3038273|然后通过Jenkins中的'manage+plugin‘上传插件|3038274|entityMap|0|LINK|mutability|MUTABLE|url|https://updates.jenkins-ci.org/download/plugins/^0|J|1C|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

use this link to download the lastest version of the plugins' hpi. <a href="https://updates.jenkins-ci.org/download/plugins/" rel="nofollow noreferrer">https://updates.jenkins-ci.org/download/plugins/</a>
Then upload the plugin through 'manage plugin' in Jenkins

Installing a plugin from the Update center results in:

<blockquote>
 Checking internet connectivity Failed to connect to
 <a href="http://www.google.com/" rel="noreferrer">http://www.google.com/</a>. Perhaps you need to configure HTTP proxy? Deploy Plugin Failure - Details hudson.util.IOException2: Failed to download from
 <a href="http://updates.jenkins-ci.org/download/plugins/deploy/1.9/deploy.hpi" rel="noreferrer">http://updates.jenkins-ci.org/download/plugins/deploy/1.9/deploy.hpi</a>
</blockquote>

Is it possible to download the plugin and install it manually into Jenkins?

How to install a plugin in Jenkins manually

服务器

Windows

Docker

从更新中心安装插件会导致：正在检查internet连接的无法连接到。也许你需要配置HTTP代理？部署插件失败-详细信息hudson.util.IOException2:无法从下载可以下载插件并将其手动安装到Jenkins中吗？

问如何在Jenkins中手动安装插件
EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Jenkins中手动安装插件EN

回答 14

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在Jenkins中手动安装插件
EN