jsoncode/dsh-jenkins
Manages multiple Jenkins servers and triggers jobs from a Settings page, model tools, or a per-workspace "Run Jenkins Job" entry, with a bilingual host + browser UI.
dsh-jenkins is a Jenkins management plugin for DeepSeek Harness that centralizes multiple servers and jobs for fast build publishing. Settings → Jenkins Config adds/edits/deletes servers (URL + token, optional TLS-skip, connection test); when a workspace root contains a dsh-jenkins.{json,js,ts} config, a footer group appears with a Jenkins logo button (Run modal: searchable server/job dropdowns, parameter form pre-filled from config, trigger + queued→building→result polling with 10-minute timeout) and a History button (last 50 runs across workspaces). Two model tools — dsh_jenkins_build and dsh_jenkins_status — let the agent trigger and check builds; logs can be viewed and builds stopped/cancelled at any time. Server tokens are encrypted with the machine-bound key $DSH_HOME/dsh-jenkins.key; the UI follows the host language (中文/English).
Install
dsh plugin --profile web add dsh-jenkinsnpm dsh-jenkins 0.1.52 verified 2026-09-03 (published same day; repository field → github.com/jsoncode/dsh-jenkins; README bilingual with 中文文档; README's local tarball example references an older 0.1.4 asset — npm latest is 0.1.52). Install: dsh plugin --profile web add dsh-jenkins, then add servers in Settings → Jenkins Config (URL + token; username defaults to admin).
Compatibility
DSH Web profile (settings.section + sidebar.footer.action); per-workspace dsh-jenkins.{json,js,ts} config files; server tokens encrypted with a machine-bound key under $DSH_HOME.
Details
- Repo: jsoncode/dsh-jenkins
- Category: Tools & Capabilities
- Stars: 0
- Version: npm dsh-jenkins 0.1.52
- Last push: 2026-09-16
- First seen: 2026-08-16
Recent updates
0.1.52 current on npm (verified 2026-09-03, published 01:26 UTC).
FAQ
- Which Jenkins servers can I manage?
- Multiple — add any number of servers in Settings with URL + token (username defaults to admin), test connections, and optionally skip TLS verification per server.
- Can the agent trigger builds itself?
- Yes — dsh_jenkins_build and dsh_jenkins_status tools let the model trigger parameterized builds and check status from the conversation.
- How are Jenkins tokens stored?
- Encrypted with the machine-bound key $DSH_HOME/dsh-jenkins.key; the settings cache is kept in plaintext and legacy settings.yaml namespaces migrate once on first run.
Alternatives
tree201/dsh-capability-inspector · woshi-Tom/dsh-status-plugin