Jenkins nodelabel plugin, where does .jpi come from?

Question

I am writing a puppet script that will automatically install a jenkins instance with nodelabel parameter plugins. It successfully loads .hpi, but the plugin still does not work.

When I install it using the web interface, I see that the working version has .hpi and .jpi files. I cannot find the link for .jpi anywhere, so I assume this is generated from .hpi. I would like to know if / how this is created during the unattended installation process so that I can simulate it in a puppet.

Answer 1

The .jpi and .hpi files are just zip files (JPI = jenkins plug in, HPI = hudson plug in). If you put .hpi in your plugins directory (possibly / var / lib / jenkins / plugins) and restart Jenkins, it will install the plug-in.

I found that Jenkins-ci.org stores .hpi files, and installing this method leaves them as .hpi files. Installation through gui changes them to .jpi.

You can also look at one of the existing puppet modules for Jenkins.