@jurislm/woodpecker-ci-plugin 2.0.1 → 2.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.codex-plugin/plugin.json +1 -1
- package/README.md +31 -4
- package/package.json +1 -1
- package/plugin.json +1 -1
- package/skills/woodpecker-ci/SKILL.md +11 -0
package/README.md
CHANGED
|
@@ -58,6 +58,7 @@ This repository also contains the portable Agent Plugin layer:
|
|
|
58
58
|
- `mcp.json` — stdio MCP server configuration.
|
|
59
59
|
- `.codex-plugin/plugin.json` — Codex compatibility fallback.
|
|
60
60
|
- `.agents/plugins/marketplace.json` — repository-root Codex marketplace entry.
|
|
61
|
+
- `.cursor-plugin/` — Cursor marketplace, plugin metadata, and MCP variables.
|
|
61
62
|
- `.mcp.json.example` — local configuration example without secrets.
|
|
62
63
|
- `skills/woodpecker-ci/SKILL.md` — service-specific tool-selection guidance.
|
|
63
64
|
- `.mcp.json` — Codex MCP registration, matching the portable `mcp.json`.
|
|
@@ -77,10 +78,36 @@ codex plugin add woodpecker-ci@woodpecker-ci-marketplace
|
|
|
77
78
|
|
|
78
79
|
The server can initialize and list its tools before credentials are set.
|
|
79
80
|
Provider calls require `WOODPECKER_URL` and `WOODPECKER_API_TOKEN` in the MCP
|
|
80
|
-
server process environment. A
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
81
|
+
server process environment. A desktop app launched by macOS does not read your
|
|
82
|
+
interactive shell configuration. Check the MCP child process, not the terminal,
|
|
83
|
+
when diagnosing missing credentials.
|
|
84
|
+
|
|
85
|
+
If an existing `~/.zshenv` exports the token, this local Codex configuration
|
|
86
|
+
launches the MCP server through zsh without copying the token into Codex config
|
|
87
|
+
or this repository. Replace the example URL with your Woodpecker API URL:
|
|
88
|
+
|
|
89
|
+
```toml
|
|
90
|
+
[mcp_servers.woodpecker-ci]
|
|
91
|
+
command = "/bin/zsh"
|
|
92
|
+
args = ["-c", "exec /usr/bin/python3 -c 'import os; keys=(\"HOME\",\"PATH\",\"TMPDIR\",\"WOODPECKER_API_TOKEN\"); env={k:os.environ[k] for k in keys if k in os.environ}; env[\"WOODPECKER_URL\"]=\"https://ci.example.com/api\"; path=env[\"HOME\"]+\"/.bun/bin/bunx\"; os.execve(path,[path,\"-y\",\"@jurislm/woodpecker-ci-plugin@latest\"],env)'"]
|
|
93
|
+
required = true
|
|
94
|
+
startup_timeout_sec = 30
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
This example needs `/usr/bin/python3` and Bun at `$HOME/.bun/bin/bunx`; replace either absolute path if needed. Python passes the token through `execve` environment, never a command argument.
|
|
98
|
+
|
|
99
|
+
`required = true` waits for this MCP server during tool discovery. Check
|
|
100
|
+
`codex mcp get woodpecker-ci`, then open a new Codex task and confirm that its
|
|
101
|
+
Woodpecker tools are present and an authenticated read succeeds. A successful
|
|
102
|
+
local stdio check alone does not verify the task's tool catalog. Keep token
|
|
103
|
+
values out of repository files and diagnostic output.
|
|
104
|
+
|
|
105
|
+
## Cursor installation
|
|
106
|
+
|
|
107
|
+
In Cursor, open Customize → Add Marketplace → Import from GitHub and enter
|
|
108
|
+
`https://github.com/jurislm/woodpecker-ci-plugin`. Add Woodpecker CI Plugin,
|
|
109
|
+
then use Configure to set `WOODPECKER_URL` and `WOODPECKER_API_TOKEN`. Cursor
|
|
110
|
+
stores the values outside this repository.
|
|
84
111
|
|
|
85
112
|
## Development
|
|
86
113
|
|
package/package.json
CHANGED
package/plugin.json
CHANGED
|
@@ -11,4 +11,15 @@ Use the Woodpecker MCP tools for live CI state and actions.
|
|
|
11
11
|
- Use read-only tools before write tools.
|
|
12
12
|
- Treat pipeline cancellation, deletion, token reset, secret changes, and repository changes as consequential.
|
|
13
13
|
- Never expose WOODPECKER_API_TOKEN or credential fields from tool results in narration.
|
|
14
|
+
- Pass tokens to local MCP processes through environment variables; never expand a token into command arguments.
|
|
14
15
|
- Report source, pipeline number, commit SHA, status, and API error status separately.
|
|
16
|
+
|
|
17
|
+
## Availability check
|
|
18
|
+
|
|
19
|
+
When asked whether the installed plugin works, record three separate results:
|
|
20
|
+
|
|
21
|
+
1. `codex mcp get woodpecker-ci` confirms the effective server command; published stdio `initialize` and `tools/list` confirm package startup and tool count.
|
|
22
|
+
2. The current Codex task must expose Woodpecker MCP methods. An empty task tool catalog is a registration failure even when the server is ready.
|
|
23
|
+
3. A registered read-only `woodpecker_get_currently_authenticated_user` call confirms provider access. Status 0 with a missing configuration name identifies the MCP child environment; HTTP 200 confirms that read only.
|
|
24
|
+
|
|
25
|
+
Read the MCP child environment when diagnosing credentials. Shell variables, an installed plugin, and a direct local MCP call do not establish current-task access. Report the package version, tool count, API status, and task registration separately.
|