Repository: github.com/0if0/JTM
Lightweight test management inside Jenkins: test cases, suites, test runs, quality gates, pipeline steps, HTML/PDF exports, and optional JUnit import. Data lives under $JENKINS_HOME/jtm/.
- Web UI at
/jtm/— dashboard, test cases, test runs, per-run detail and matrix - Pipeline steps —
publishJTMResults,enforceQualityGate,updateTestCase - Imports — CSV / structured text, JUnit XML (post-build recorder)
- Reports — single-run and multi-run flat export (HTML + PDF) with optional branding
- Permissions — View / Execute / Edit / Admin (matrix-friendly)
- REST-style API for automation (see plugin UI and
JtmApiAction)
Dashboard — project scope, quality overview KPIs, and insights.
Charts and recent activity — status mix, failure trend over time, recent test runs, and run progress.
Run progress — pick a run, see outcome counts and pass-rate donut for that build.
- Jenkins 2.541.3 or compatible (see
pom.xml) - Java 17+ for building the plugin
mvn clean verify
# HPI: target/jtm.hpi
mvn hpi:run
# Open http://localhost:8080/jtm/
- Build
target/jtm.hpi - Manage Jenkins → Plugins → Advanced → upload the HPI → restart if prompted
- Grant JTM permissions under Manage Jenkins → Security
More detail: BUILD.md (permissions, pipeline example, data layout).
All three steps are available from Jenkins' Pipeline Syntax / Snippet Generator. publishJTMResults reads a workspace-relative JSON file, stores a JTM test run, and returns its run ID.
publishJTMResults: requiredresultsFile;updateTestCases(defaulttrue),failOnParseError(defaultfalse), andcreateMissingTestCases(defaultfalse).enforceQualityGate: optionalrunId(otherwise the build's published run orJTM_RUN_ID);minPassRate(default95),maxFailures(default-1, unlimited),blockOnBlocked(defaultfalse),blockOnCritical(defaulttrue), andblockOnFailure(defaulttrue).updateTestCase: requiredtestCaseIdandstatus(PENDING,PASSED,FAILED,BLOCKED,SKIPPED, orFALSE_POSITIVE); optionalcomment,durationMs(default-1), andfailOnNotFound(defaultfalse).
The results JSON contains runName, release, branch, commitId, environment, and a results array. Each result has testCaseId, status, durationMs, and optional comment, errorMessage, and stackTrace.
| Path | Purpose |
|---|---|
pom.xml, src/ |
Jenkins plugin (Maven project at repository root, .hpi in target/) |
docs/images/ |
README screenshots |
e2e/ |
Playwright tests against a running Jenkins (optional CI) |
scripts/ |
Helper scripts used by GitLab deploy jobs (optional) |
Optional. Requires a reachable Jenkins with JTM installed and credentials.
cd e2e
npm ci
npx playwright test
Set JENKINS_BASE_URL (and optionally JENKINS_USER / JENKINS_PASSWORD) as in e2e/playwright.config.ts.
- GitHub Actions: .github/workflows/ci.yml —
mvn verifyon a JDK matrix (21/25), plus optional Playwright smoke if Jenkins secrets are configured - GitLab CI: .gitlab-ci.yml — build, optional deploy to Jenkins, optional Playwright (if you still use GitLab)
mvn verify runs SpotBugs from the Jenkins plugin parent and fails the build on findings (spotbugs.failOnError=true).
See CONTRIBUTING.md.
MIT (see also pom.xml).
pom.xml lists this repository as home (<url> and <scm>). If you fork to another GitHub org or user, update those entries and the CI badge above to match.


