dsh-jenkins
In a curated listMaintenance: Activejsoncode/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 plugin add dsh-jenkinsInstall
dsh has no central install command — add this plugin’s entry (documented in its README) to your profile or patch config, then restart.
How installs work3
stars
1
forks
JavaScript
Language
2026-08-16
Created
2026-11-11
Last push
README
dsh-jenkins
dsh-jenkins is a Jenkins management plugin built on the DeepSeek Harness (DSH) host, centralizing multiple servers and jobs for fast build publishing.
- Multi-server / multi-job management — configure and manage multiple Jenkins servers and jobs in one place
- One-click publishing — trigger parameterized builds, track queue → building → result in real time
- Logs & operations — view build logs, stop or cancel builds at any time
- Bilingual UI — follows the host interface language (中文 / English)
Available from the Settings page (the single UI entry since DSH 0.2.2-rc.1) and model tools.
Preview
Screenshots of the Settings page, workspace entry and run/history modals: see preview.md.
Features
- Settings → Jenkins Config page (
settings.section— the single UI entry): a "Jenkins Config" row (with a Jenkins-logo nav icon) in the settings dialog's left menu; the page embeds four tabs — Publish / Config / Local records / Server history. Its title row carries the task status capsules (building / done-unread / "Update" pill) and a workspace picker (defaults to the current session's workspace, manually switchable). Add / edit / delete multiple servers (URL, username, Token), test connections, skip TLS verification. Only Server URL and Token are required (username defaults toadmin). Secondary modals (build log / server editor / project config / update changelog) render as top-level viewport overlays, never clipped by the settings panel. - Project Config (
$DSH_HOME/dsh-jenkins-map.json): every project's publish targets in one file — project name → target array, with elements identical to a workspace config file ({ name?, job, server, environments }). Each env can carry anamedisplay label (e.g.uat环境/prod灰度/prod环境) and the number of envs is unlimited (an empty name falls back to UAT / Prod / Env N). Adsh-jenkins.json/js/tsin a project root is discovered automatically (folder name as the project name, missing-only — nothing you edited is overwritten), so there is usually nothing to maintain by hand; to edit, click Edit map on the Project Config row of the Config tab (form / JSON). See Project config. - Publish tab (inside the settings page): just three rows — project → server →
job — then the parameter form, build triggering and status polling (queued →
building → result, 10-minute timeout). The env has no row of its own: each env
in a project config is a server, so env selection lives in the Server
dropdown — whose labels show only the plugin's server name (never a mix of the
config's env name and the server name), and picking one switches the job / params
to that env. Config
serverrefs are matched against configured servers by name → id → full URL → domain (the domain level ignores scheme, port and context path). The dropdown shows the intersection of the servers referenced by the project config and the servers configured in the plugin; the last parameters are remembered per project and auto-echoed next time. - Model tools (docs/develop/basic/tool):
dsh_jenkins_build,dsh_jenkins_status. - Config (docs/develop/basic/config): Schemastery
Config+ a plugin data file$DSH_HOME/dsh-jenkins.json(server tokens encrypted with the machine-bound key$DSH_HOME/dsh-jenkins.key, cache in plaintext); the project config is its own file$DSH_HOME/dsh-jenkins-map.json(plaintext, hand-editable). Since DSH 0.2.2-rc.1 the legacysettings.yamldocument is migrated by the host framework itself — the plugin no longer reads or writes it (when the data file is missing it is seeded from the bundle entry'sconfig.servers); a legacyprojectsfield insidedsh-jenkins.jsonis migrated into the new file (missing-only). - Packaging (docs/develop/basic/publish):
dsh.bundle+dsh.client(web) manifests.
Structure
├── src/host/*.ts # Host half: index.ts (entry), jenkins.ts (curl core), ops.ts (op dispatch), project-map.ts (project config file), projects.ts (normalize/merge), workspace-config.ts, types.ts
├── src/client/*.tsx # Browser half (React TSX): settings.section entry page (embedded 4 tabs), publish/project/history tabs, secondary modals
├── lib/index.js # Host half build artifact (tsdown, ESM), committed for git installs
├── lib/client.js # Browser half build artifact (tsdown → __ModuleLoader__ factory), committed
├── lib/types/ # Type declarations (generated by tsc -b)
├── scripts/ # verify-client.mjs (host-seed simulation check) + isolated tests
├── examples/ # sample configs: dsh-jenkins.json (workspace array), dsh-jenkins-map.json (central map)
├── tsdown.config.ts # tsdown build config (node half + client bundle banner wrapper)
├── tsconfig.json # solution: references tsconfig.host.json / tsconfig.client.json
├── cordis.patch.yml # Bundle patch: plugin row referenced by package name (no paths)
├── package.json # dsh.bundle + dsh.client(web) manifests + peerDependencies
├── README.md # This file (English)
├── README.zh.md # 中文文档
└── preview.md # Screenshot preview (references assets/preview/*.png)
Workspace config file (dsh-jenkins.json / .js / .ts)
Place it in the workspace root. It is an array; each element is one deploy
target (job + server + environments params). .json is parsed directly; .js / .ts
are evaluated with node (CJS module.exports or ESM export default):
[
{
"job": "build-app",
"server": "http://uat.example.com",
[Read the full README on GitHub →](https://github.com/jsoncode/dsh-jenkins)More in Web & Browser
anysearch-dsh
by anysearch-team
AnySearch web search provider and advanced search tools for DeepSeek Harness (DSH)
dsh-find-plugin
by awesome-dsh-plugin
In-agent plugin discovery: live GitHub repository search scoped to the official `dsh-plugin` topic, star-ranked; every result comes with a ready-to-run `dsh plugin add` command.
fnos-dsh
by fnosp
Multi-source web search and fetch failover for DeepSeek Harness sessions: takes over the session searchProvider and fetchProvider seams and tries configured sources in a chosen order — TinyFish, Tavily and the official search as a fallback that always participates and can be repositioned but not removed. Multiple API keys per platform are spread round-robin, usage snapshots drive pre-flight exclusion of exhausted accounts, and per-request timeouts plus same-platform retry control failover granularity. Web fetching runs local HTTP first, then falls back to TinyFish Fetch server-side rendering and Tavily Extract, so pages still load when local egress is blocked by proxy or DNS policies. A per-platform panel shows key usage and plan limits. Install from npm with `dsh plugin --profile web add @tnnevol/dsh-failover-search`.
modsearch
by liustack
Web/X 搜索与抓取桥:为纯文本 coding agent 提供结构化 JSON 证据(search/fetch/citations),引擎可选 Antigravity CLI(免 key)/带 key 引擎/X(Grok Build 登录态)。
