be-jenkins-deploy

Steps

1. Resolve Jenkins job

If the job name is not in the user request, check conversation history for prior Jenkins calls (e.g., mcp__jenkins__triggerBuild or mcp__jenkins__getJob calls). If still unknown, ask: "Which Jenkins job should I deploy to?"

2. Resolve branch

Use the first source that yields a result, in priority order:

1. Explicit arg — branch name passed directly by the user
2. PR clue — if conversation contains a PR URL (github.com/.../pull/N) or PR number, extract the head branch via gh pr view <N> --json headRefName -q .headRefName. If only a PR title is available, first resolve it to a PR number with gh pr list --search "<PR title>" --json number,title (pick the matching PR), then run gh pr view <N> --json headRefName -q .headRefName
3. Local git — git branch --show-current

If all three fail, ask the user.

3. Fetch job parameters

Call mcp__jenkins__getJob with the job name. Prefer the job's parameter definitions (if present) to determine the parameter schema and any declared defaults. Build the trigger payload from those defaults, overriding only the branch parameter with the current branch.