Home/Blog/The Plugin Marketplace: 1,000+ Jenkins Plugins at Your Fingertips
pluginsfeaturedevops

The Plugin Marketplace: 1,000+ Jenkins Plugins at Your Fingertips

A deep dive into how Plumber's built-in plugin marketplace works: live data from plugins.jenkins.io, one-click install, paginated browsing, and how plugins actually extend the execution engine.

AO

Abi O.

Creator

14 May 20256 min read

When we first shipped plugin support in Plumber, it was a simple file browser — you picked a .hpi file from your disk and Plumber loaded it. Functional, but far from delightful. In the latest release we replaced that with a full marketplace.

Live data, always current

The marketplace calls https://plugins.jenkins.io/api/plugins/?limit=1000&sortBy=installs on every open, with a 30-minute local cache. This means you're always looking at real install counts, real descriptions, and real versions — not a handpicked list we have to maintain.

The top 1,000 plugins by install count covers the vast majority of what any Jenkins shop actually uses:

PluginCategoryInstalls
PipelinePipeline3M+
Credentials BindingSecurity2.1M+
JUnitQuality2.3M+
GitSource Control2M+
Docker PipelineContainers1.6M+

Search and filter

The search box filters across plugin name, ID, description, and labels simultaneously. Category filters map from the Jenkins plugin API's label taxonomy:

  • Source Control → scm, version-control
  • Containers → docker, kubernetes
  • Security → security, authentication, credentials
  • IaC → terraform, configuration-as-code

Unknown plugins get a deterministic colour and abbreviation generated from their name, so every card looks distinct.

One-click install

Clicking Install on any card:

  1. Downloads the .hpi from updates.jenkins.io directly
  2. Imports the plugin into Plumber's plugin registry
  3. Makes the plugin's declared step names available in subsequent pipeline runs

The plugin is stored in Plumber's data directory, not your project directory, so it persists across workspaces.

Plugin detail pages

Every card is clickable. The detail page shows the full description (HTML-stripped from the API), the plugin's version, all its labels as tags, and a direct link to its page on plugins.jenkins.io. If you want to read the changelog or check the issue tracker before installing, one click takes you there.

Pagination for speed

The grid renders 30 plugins per page. This turned out to be critical — rendering 1,000 Fyne widgets at once was the single biggest source of UI lag in early builds. With pagination, the marketplace opens instantly and page turns are smooth.

Benchmark: 1000 cards rendered at once → ~4.2s to first frame Benchmark: 30 cards per page → ~38ms to first frame

What plugins do you want to see better supported? Let us know.