Jenkins
Connect Jenkins to BuildButler — choose between the Local (self-hosted) or Cloud (hosted) plugin.
BuildButler offers two Jenkins plugins. Both ingest the same rich set of data — builds, tests, pipeline stages, agents, and logs — but differ in how that data is stored and where you view it.
Which plugin should I use?
| Jenkins Local | Jenkins Cloud | |
|---|---|---|
| Storage | Your own PostgreSQL database | BuildButler hosted, isolated per org |
| Viewed in | Jenkins UI (plugin dashboard) | BuildButler web app |
| Internet required | No — fully self-contained | Yes — data sent to BB backend |
| Setup complexity | Bring your own Postgres | Sign up and install plugin |
| Best for | Air-gapped / on-prem strict environments | Teams wanting zero infrastructure |
Data collected
Both plugins collect the same data from Jenkins:
- Build results, status, duration, and branch
- Test results (JUnit, TestNG, etc.) with pass/fail/skip counts
- Pipeline stage execution times
- Agent status and availability
- Build console logs