jenkins-deploy-skill

Merge code to a deploy branch and trigger Jenkins jobs via buildWithParameters.

53|4|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/maimingliang/jenkins-deploy-skill --skill jenkins-deploy-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jenkins-deploy-skill
Source: https://github.com/maimingliang/jenkins-deploy-skill/tree/main
Command: npx skills add https://github.com/maimingliang/jenkins-deploy-skill --skill jenkins-deploy-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the repetitive context switching needed to merge/push code and trigger Jenkins builds for environment releases like dev, test, and pre.

Core Features & Use Cases

  • Branch integration + promotion flow: merges/cascades from the right upstream branch into the requested deploy branch (e.g., dev->test->pre) before triggering Jenkins.
  • Secure Jenkins credential handling: pulls Jenkins API tokens from Windows Credential Manager, macOS Keychain, or CI env vars, and uses crumb handling when available.
  • Platform-aware triggering: triggers Jenkins via REST API using a PowerShell script on Windows and a Python script on macOS/Linux, including job and branch-parameter support.

Use case: you are on your feature branch with local changes and you want an AI to publish the merged result to the dev environment and trigger the correct Jenkins job automatically.

Quick Start

Tell your AI: "帮我部署到 dev 环境".

Frequently Asked Questions about jenkins-deploy-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate merging a feature branch and triggering a Jenkins deployment?

You can automate Jenkins deployments by merging upstream branches into a target deploy branch and triggering the job via the buildWithParameters REST API, which handles dev, test, and pre environments automatically.

How does Jenkins API token management work for automated deployments?

Jenkins API token management for deployments uses Windows Credential Manager, macOS Keychain, or CI environment variables as fallback, applying crumb handling during REST API triggering for secure authentication.

Can I trigger Jenkins builds with parameters from both Windows and macOS?

Yes, triggering Jenkins builds with parameters works cross-platform using a PowerShell script on Windows and a Python script on macOS/Linux, passing job and branch parameters through the REST API.

What is the branch promotion flow for cascading code across dev, test, and pre environments?

Branch promotion cascades code by merging from the right upstream branch into the requested deploy branch, such as dev to test to pre, before triggering the corresponding Jenkins job for environment releases.

Does automated Jenkins deployment support multi-project config layouts?

Yes, automated Jenkins deployment supports both single-project and multi-project config layouts driven by config.json, including optional per-project job overrides for branch and credential selection.

What guardrails prevent accidental production deployments during Jenkins automation?

Jenkins deployment automation enforces non-production usage guardrails and a strict no-force push policy, restricting automated triggering to dev, test, and pre environments to prevent accidental production releases.