Ci Health

CI Health Report: $ARGUMENTS

1. controllers_list — find all CI controllers (Jenkins instances)

1. For each controller, pull analytics:

a. controllers_data_get(ci2) — System Information (version, plugins, nodes, executors) b. controllers_data_get(ci3) — System Health (disk, threads, plugins) c. controllers_data_get(ci4) — Runs Overview (active, queued, wait times) NOTE: ci5, ci6, ci7 may return empty data. If they do, skip gracefully. d. report_drilldown_get(pluginsInfo) — plugin health details

1. If specific component:

a. components_search — find the component b. runs_list(limit=20) — pull recent run history c. Calculate pass rate from run statuses d. security_issues_all_get — security posture

1. If 'org':

a. components_list — all components b. Per component: runs_list(limit=10) — recent runs c. security_issues_all_get — org-wide security

1. Calculate and report:

• Pass rate: Per CI tool, per component. Break out GitHub Actions

vs. CloudBees Workflows vs. Jenkins.

• Failure patterns: Common failure steps/categories across runs
• Controller health: System health score, plugin status, version
• Security posture: Open findings count and severity
• Queue time: From ci4 — how long runs wait before starting

1. Provide a "CI Health Score" (0-100) based on:

• Pass rate (weight: 35%)
• Controller health (weight: 20%)
• Security posture (weight: 25%)
• Queue efficiency (weight: 20%)

1. List top 3 actionable recommendations
2. Offer next actions:

• "/triage [component]" for components with low pass rates
• "/security-scan" if security posture is poor
• Post health report to Slack

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: cloudbees-oss
• Source: cloudbees-oss/devops-agent-kit
• License: Apache-2.0

Install and usage instructions live in the source repository linked above.