dsh-jenkins-panel

Operating Jenkins from within a dsh conversation used to mean copying URLs, manually scrolling through logs, and showing AI screenshots of FAILURE states expecting a guess. dsh-jenkins-panel collapses the entire pipeline into a single plugin: once the model sees 22 jenkins_* tools it can trigger builds, poll status, pull logs and artifacts, and resolve candidate jobs—all trigger records persist in a registry that survives restarts.

The official right-side panel brings visualization into dsh-native layout: an overview section refreshes chat-triggered build statuses in real time, a jobs section supports multi-connection switching with multi-level collapsible trees, and a build-detail section offers log tailing, segmented browsing, auto-follow, artifact download, and workspace cleanup—no extra browser tab needed.

The most practical closed loop is automatic failure analysis: when a triggered build ends in FAILURE the plugin pushes an analysis task back into the triggering session, where the AI reads logs read-only and emits a structured summary (conclusion, key errors, likely causes, fix suggestions). Connection and credential management lives in the dsh settings page with tokens stored via credential-ref so plain-text secrets never land in config. Ideal for CI/CD engineers and DevOps teams who interact with Jenkins frequently and want the AI to act, not just observe.