jenkins
Skill1 starsChanged 16 days agoApache-2.0View on GitHub
Interact with Jenkins CI via REST API. Use when checking build status, viewing test failures, reading console output, triggering builds, watching build progress, viewing pipeline stages, listing jobs, or managing the build queue on a Jenkins server.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- infiniumtek/code-review-agenttheir own version, first seen Oct 25, 2026
- DongDuong2001/pudo-code-systemtheir own version, first seen Oct 13, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- avantmedialtd/skillstheir own version, first seen Oct 9, 2026
- Mark20251104/skillstheir own version, first seen Apr 22, 2026
- isYaoNoistu/claudecode-skillstheir own version, first seen Mar 9, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- G1Joshi/Agent-Skills★ 15same name
- koderover/devops-skills★ 7same name
- DongDuong2001/pudo-code-system★ 5same name
- infiniumtek/code-review-agent★ 4same name
- avantmedialtd/skills★ 1same name
- isYaoNoistu/claudecode-skills★ 1same name
- Mark20251104/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-chatSkill
- argocdSkill
- code-reviewSkill
- commitSkill
- dependency-trackSkill
- financeSkill
- handoffSkill
- java-21-to-25-migrationSkill
- jiraSkill
- perplexitySkill
- pr-readySkill
- researchSkill
- shipSkill
- skanetrafikenSkill
- sonarqubeSkill
- tddSkill
- to-tasksSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run ./setup.sh from the repo root (recommended), or create config files manually:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Jenkins CI
Interact with a Jenkins CI server via its REST API.
Configuration
Run ./setup.sh from the repo root (recommended), or create config files manually:
mkdir -p ~/.boring/jenkins
echo 'https://your-jenkins.example.com' > ~/.boring/jenkins/url
echo 'your-username' > ~/.boring/jenkins/user
echo 'your-api-token' > ~/.boring/jenkins/token
chmod 600 ~/.boring/jenkins/tokenObtain an API token: Log in → Your Username → Configure → API Token → Add new Token → Generate.
Job path format
Paths use / to separate folders:
MyOrg/my-service/main— main branchMyOrg/my-service/PR-42— pull requestMyOrg/my-service/feature%2Fmy-branch— URL-encode slashes in branch names
Scripts
Build status
scripts/jenkins-build-status.sh <job-path> [build-number]Test failures
scripts/jenkins-test-failures.sh <job-path> [build-number] [--full]--full includes complete stack traces.
Console output
scripts/jenkins-console.sh <job-path> [build-number] [grep-pattern]Trigger a build
scripts/jenkins-trigger.sh <job-path> [--param KEY=VALUE]...Watch build progress
scripts/jenkins-watch.sh <job-path> [build-number]Polls until the build finishes and exits 0 on success, 1 on failure.
Build history
scripts/jenkins-build-history.sh <job-path> [count]Pipeline stages
scripts/jenkins-stages.sh <job-path> [build-number]Shows stage names with pass/fail status (requires Pipeline plugin).
List jobs
scripts/jenkins-list-jobs.sh [folder-path] [--depth N]Build queue
scripts/jenkins-queue.shAbort a build
scripts/jenkins-abort.sh <job-path> [build-number]Raw API
scripts/jenkins-api.sh <endpoint> [curl-options...]Typical workflow
S=scripts
$S/jenkins-build-status.sh "MyOrg/my-service/PR-42"
$S/jenkins-test-failures.sh "MyOrg/my-service/PR-42"
$S/jenkins-console.sh "MyOrg/my-service/PR-42" lastBuild "ERROR"
$S/jenkins-stages.sh "MyOrg/my-service/PR-42"
$S/jenkins-trigger.sh "MyOrg/my-service/PR-42"
$S/jenkins-watch.sh "MyOrg/my-service/PR-42"API endpoints reference
Append to job URL:
/api/json— metadata/lastBuild/api/json— last build/lastBuild/consoleText— console/lastBuild/testReport/api/json— test results/build— trigger (POST)/buildWithParameters?KEY=VALUE— parameterized trigger (POST)/lastBuild/wfapi/describe— pipeline stages/stop— abort (POST)
Query params: tree=field[sub], depth=N
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.