Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Interact with Jenkins CI/CD server via REST API. Use when you need to trigger builds, check build status, view console output, manage jobs, or monitor Jenkin...
Interact with Jenkins CI/CD server via REST API. Use when you need to trigger builds, check build status, view console output, manage jobs, or monitor Jenkin...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Interact with Jenkins CI/CD server through REST API.
JENKINS_URL (example: https://jenkins.example.com) JENKINS_USER (your Jenkins username) JENKINS_API_TOKEN (API token from Jenkins user settings)
node {baseDir}/scripts/jenkins.mjs jobs node {baseDir}/scripts/jenkins.mjs jobs --pattern "deploy-*"
node {baseDir}/scripts/jenkins.mjs build --job "my-job" node {baseDir}/scripts/jenkins.mjs build --job "my-job" --params '{"BRANCH":"main","ENV":"dev"}'
node {baseDir}/scripts/jenkins.mjs status --job "my-job" node {baseDir}/scripts/jenkins.mjs status --job "my-job" --build 123 node {baseDir}/scripts/jenkins.mjs status --job "my-job" --last
node {baseDir}/scripts/jenkins.mjs console --job "my-job" --build 123 node {baseDir}/scripts/jenkins.mjs console --job "my-job" --last --tail 50
node {baseDir}/scripts/jenkins.mjs stop --job "my-job" --build 123
node {baseDir}/scripts/jenkins.mjs queue
node {baseDir}/scripts/jenkins.mjs nodes
URL and credentials are variables by design for cross-environment deployment. API responses are output as JSON. For parameterized builds, use --params with JSON string.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.