- Home
- Skills
- DevOps & Cloud
- Jenkins CI/CD & Build Orchestration Pro
Works with the AI Agents you already use
Jenkins CI/CD & Build Orchestration Pro
Connect your AI agent to enterprise Jenkins controllers. Manage 53 tools covering jobs, builds, queue inspection, build agent fleets, pipeline replay, and controller administration.
$19
Jenkins CI/CD & Build Orchestration Pro
Example session with this skill installed
Check the status of the 'frontend-build' job, find the last failed build, and show me the pipeline stages where it broke.
- Read your context and instructions
- Compiled the jenkins ci cd
I have retrieved the status for the 'frontend-build' job and identified the latest failure in build #42. The pipeline failed during the 'Integration Tests' stage after running for 4 minutes.
Build Failure Analysis: frontend-build #42
| Stage | Status | Duration | Error Summary |
|---|---|---|---|
| Checkout | SUCCESS | 12s | Code pulled from main branch |
| Install Dependencies | SUCCESS | 1m 45s | All npm packages resolved |
| Unit Tests | SUCCESS | 2m 10s | 450 tests passed |
| Integration Tests | FAILED | 4m 05s | Connection timeout on port 8080 |
| Docker Build | SKIPPED | 0s | Stage not reached |
| Push to Registry | SKIPPED | 0s | Stage not reached |
Build Metadata
- Result: FAILURE
- Timestamp: 2023-10-27 14:22:01
- Trigger: Commit
a1b2c3dby @developer_name - Log Snippet:
[ERROR] Failed to connect to localhost/127.0.0.1:8080. Connection refused.
Next steps
- Run
jenkins_get_build_log(job_name="frontend-build", build_number=42, start_line=500)to see the full stack trace. - Use
jenkins_replay_pipelineto test a fix for the integration test timeout without a new commit. - Check agent health with
jenkins_get_node_infoif this appears to be a network infrastructure issue.
Connects securely to your tools. The creator never sees your data.
About this skill
🚀 Production Workflows
- Parameterized Build Triggers & Queue Scheduling: Triggers matrix and parameterized jobs with validation, monitoring build queue position until execution.
- Console Log Failure Analysis: Scans thousands of console output lines, isolates stack traces, and pinpoints build failures in seconds.
- Flaky Stage Detection & Script Replay: Inspects Declarative Pipeline stage execution durations and replays pipelines with hotfixed scripts.
- Build Agent Fleet & Executor Health: Audits agent offline causes, inspects JVM executors, and safely takes nodes offline for patching.
- Release Promotion & Graceful Restart: Gating release builds, entering quiet down maintenance mode, and executing safe controller restarts.
🛡️ Safety & Governance
- Read-only autonomous log inspection, queue queries, and stage audits.
- Confirmation-gated triggers, build aborts, node changes, and restarts.
Launch via: uvx jenkins-mcp
Requires JENKINS_URL and API token setup. Must run scripts/verify_env.py before first use. Destructive operations require explicit operator confirmation.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 16 days ago
Requires