jenkins-sre

Diagnose Jenkins runtime issues across controllers, agents, and credentials.

Updated Mar 18, 2026

Search Tags:#credentials #jenkins #sre #websocket #agent-connectivity #runtime-troubleshooting #controller-health

Ready to run

npx skills add https://github.com/Canepro/codex-skills --skill jenkins-sre

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jenkins-sre
Source: https://github.com/Canepro/codex-skills/tree/main/skills/jenkins-sre
Command: npx skills add https://github.com/Canepro/codex-skills --skill jenkins-sre

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Jenkins runtime and control-plane issues such as offline nodes, flaky agents, credential problems, WebSocket handshakes, and unhealthy controllers are diagnosed and triaged to avoid conflating problems with pipeline logic.

Core Features & Use Cases

Identify the exact Jenkins surface: controller health, agent connectivity, credentials, or queue/executor behavior.
Verify controller state, including health, executor availability, queue backlog, and node connection status.
Distinguish between controller, agent, and secret problems and provide targeted remediation guidance.

Quick Start

Describe the Jenkins runtime issue and provide any relevant URLs, node names, and symptoms to begin targeted guidance.

Frequently Asked Questions about jenkins-sre

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose Jenkins controller health issues and agent connectivity problems?▼

To diagnose Jenkins controller health and agent connectivity issues, verify controller state, executor availability, queue backlog, and node connection status. Identify the exact surface where the problem manifests to provide targeted remediation guidance.

Why does my Jenkins agent stay offline and how can I fix it?▼

Jenkins agents may stay offline due to controller health, WebSocket handshake, or credential problems. Distinguish between controller, agent, and secret problems to apply the correct remediation rather than conflating issues with pipeline logic.

What is the best way to troubleshoot Jenkins runtime problems without conflating them with pipeline logic?▼

The best way to troubleshoot Jenkins runtime problems is to enforce step-by-step surface identification, state checks, and escalation hints with references to runtime patterns. This separates control-plane issues from pipeline logic.

Can I use this approach to fix flaky Jenkins agents and credential problems?▼

Yes, you can fix flaky Jenkins agents and credential problems by distinguishing between controller, agent, and secret problems. This targeted remediation approach identifies whether the issue stems from credentials, WebSocket handshakes, or unhealthy controllers.

How do I start troubleshooting a Jenkins queue backlog and offline nodes?▼

Start troubleshooting a Jenkins queue backlog and offline nodes by describing the runtime issue and providing relevant URLs, node names, and symptoms. This initiates targeted guidance to verify controller state and executor availability.