Does build-monitor-plugin run?

build-monitor-plugin has not been fully verified yet. No recorded run has produced a verdict yet.

How did Argusic test build-monitor-plugin?

On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.

Where is the evidence for build-monitor-plugin?

All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

build-monitor-plugin

Jenkins Build Monitor Plugin

Not yet testedsource: GitHub homepageJavaMITcommit 9b89ddc60c59

Java, MIT licensed. The project labels itself: continuous delivery, continuous improvement, continuous integration, continuous testing and jenkins ci.

build-monitor-plugin has not been verified yet.

Measured by Argusic on a fresh machine every time. Every number links to its evidence.

At a glance

verdict: Not yet tested
Argusic Score: not scored yet
recorded runs: 0
last tested: -
stars: 727
forks: 295
open issues: 125
watchers: 36
size: 22 MB
created: 2013-07-06
last push: 2026-10-05

Subject data from GitHub, linked at the top of this page, refreshed 2026-10-08. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

No recorded runs.

Topics (from GitHub)

continuous-delivery continuous-improvement continuous-integration continuous-testing jenkins-ci

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/build-monitor-plugin.svg)](https://argusic.com/subject/build-monitor-plugin)

Questions

Does build-monitor-plugin run?: build-monitor-plugin has not been fully verified yet. No recorded run has produced a verdict yet.
How did Argusic test build-monitor-plugin?: On a fresh, disposable machine, with every command recorded. 0 attempts are recorded, and the full method is on the methodology page.
Where is the evidence for build-monitor-plugin?: All 0 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.