部署与云服务
create-pipeline
Generate Harness v0 Pipeline YAML for CI/CD workflows and create them via MCP. Supports CI stages (build, test, Docker push), CD stages (Kubernetes, Helm, ECS, serverless), approval gates, parallel execution, matrix strategies, and failure rollback. Use when asked to create a pipeline, build pipeline, deployment pipeline, CI/CD workflow, or set up Harness pipelines. Do NOT use for v1 simplified pipelines (use create-pipeline-v1). Trigger phrases: create pipeline, build pipeline, deployment pipeline, CI/CD, Harness pipeline, Kubernetes deploy pipeline.
harness · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add harness/harness-skills --skill create-pipeline技能说明
name: create-pipeline description: >- Generate Harness v0 Pipeline YAML for CI/CD workflows and create them via MCP. Supports CI stages (build, test, Docker push), CD stages (Kubernetes, Helm, ECS, serverless), approval gates, parallel execution, matrix strategies, and failure rollback. Use when asked to create a pipeline, build pipeline, deployment pipeline, CI/CD workflow, or set up Harness pipelines. Do NOT use for v1 simplified pipelines (use create-pipeline-v1). Trigger phrases: create pipeline, build pipeline, deployment pipeline, CI/CD, Harness pipeline, Kubernetes deploy pipeline. metadata: author: Harness version: 2.2.0 mcp-server: harness-mcp-v2 license: Apache-2.0 compatibility: Requires Harness MCP v2 server (harness-mcp-v2)
Create Pipeline
Generate Harness v0 Pipeline YAML and optionally push to Harness via MCP.
Instructions
- Analyze codebase (if source code is available) - Scan the project to auto-detect language, build tools, test frameworks, containerization, deployment manifests, and target infrastructure. Use the detection tables and decision tree in
references/codebase-analysis.mdto determine:- Language and runtime version (package.json → Node.js, go.mod → Go, pom.xml → Java, etc.)
- Build commands and base images
- Test framework and report format (Jest → JUnit, pytest → JUnit XML, etc.)
- Linter and formatter (ESLint, Prettier, Ruff, etc.)
- Dockerfile presence and registry type (Docker Hub, ECR, GCR, ACR)
- Deployment manifests → Harness service/deployment type (k8s manifests → Kubernetes, Chart.yaml → NativeHelm, task-definition.json → ECS, serverless.yml → ServerlessAwsLambda)
- Existing CI/CD configs for migration (GitHub Actions, Jenkins, GitLab CI, etc.)
- Clarify requirements - Confirm detected settings with the user. Ask about anything that couldn't be auto-detected — do not guess or use placeholders. If the user's request is ambiguous, ask before generating YAML. Examples of what to ask when missing:
- Deployment target / infrastructure: region (e.g. us-east-1), cluster name or ID, account ID (e.g. AWS account for ECR/ECS)
- Registry: which registry (Docker Hub, ECR, GCR, ACR), registry identifier/URL, repo path
- Cloud provider: which account, region, and resource identifiers for connectors/infrastructure
- Approval gates, notification channels if relevant
Critical rule: Never hardcode placeholder values (e.g.
123456789012,us-east-1,my-cluster) for deployment target, region, registry, or cluster when the user did not specify them — ask the user instead. If the user did not specify region, account ID, cluster, or registry (e.g. "deploys to ECS" with no region or cluster), ask the user for those values before generating YAML.
- Select native steps - Always prefer Harness native steps over
RunorShellScriptsteps. Consultreferences/native-steps.mdfor the full mapping. Key rules:- Docker build/push → use
BuildAndPushDockerRegistry/BuildAndPushECR/BuildAndPushGCR/BuildAndPushACR(neverRun: docker build && docker push) - K8s deploy → use
K8sRollingDeploy/K8sBlueGreenDeploy/K8sCanaryDeploy(neverRun: kubectl apply) - Helm deploy → use
HelmDeploy(neverRun: helm upgrade --install) - ECS deploy → use
EcsRollingDeploy(neverRun: aws ecs update-service) - Terraform → use
TerraformPlan/TerraformApply(neverRun: terraform apply) - Security scanning → use native STO steps (
AquaTrivy,Snyk,Sonarqube,Semgrep, etc.) - Uploads → use
S3Upload/GCSUpload(neverRun: aws s3 cp) - Approvals → use
HarnessApproval/JiraApproval(never polling scripts) - Ticketing → use
JiraCreate/ServiceNowCreate(neverRun: curl) - Use
Runsteps only for custom build/test/lint commands with no native equivalent - Test steps: Any Run step that runs unit or integration tests must include a
reportsblock (e.g.type: JUnit,spec.paths) so Harness can capture results; seereferences/codebase-analysis.mdfor framework → report path.
- Docker build/push → use
- Generate valid YAML following the structure below, using the detected build/test/deploy commands. Validation rules: (a) Stage names must match
^[a-zA-Z_0-9-.][-0-9a-zA-Z_\\s.]{0,127}$— use only letters, numbers, spaces, hyphens, underscores, or periods (no commas). (b) Every CI and CD stage must include afailureStrategiesarray (Approval stages do not require one). For CI useMarkAsFailure(neverIgnore— it hides failures); for CD useStageRollback. - Optionally create via MCP — First verify the project exists (see "Creating via MCP" section below), then use
harness_createwith resource_typepipelineandbody: { yamlPipeline: "<YAML string>" }
Pipeline Structure
pipeline:
identifier: my_pipeline # ^[a-zA-Z_][0-9a-zA-Z_]{0,127}$
name: My Pipeline
orgIdentifier: default
projectIdentifier: my_project
tags: {}
properties:
ci:
codebase: # Required for CI stages
connectorRef: github_connector
repoName: my-repo
build:
type: branch
spec:
branch: <+trigger.branch>
stages:
- stage: ...
Stage Types
CI Stage (type: CI)
- stage:
identifier: build
name: Build
type: CI
spec:
cloneCodebase: true
platform:
os: Linux
arch: Amd64
runtime:
type: Cloud # Cloud, Kubernetes, VM, Docker
spec: {}
execution:
steps:
- step: ...
failureStrategies:
- onFailure:
errors: [AllErrors]
action:
type: MarkAsFailure
CD Stage (type: Deployment)
- stage:
identifier: deploy
name: Deploy
type: Deployment
spec:
deploymentType: Kubernetes # Kubernetes, NativeHelm, ECS, ServerlessAwsLambda, Ssh, WinRm, AzureWebApp
阅读完整来源 ↗