create-pipeline-v1
Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps. Supports CI stages (run, run-test, background), CD stages (service/environment with action steps for K8s, Helm, ECS), approval (stage-level and inline), parallel execution, matrix/for/while strategies, caching, volumes, and templates. Use when asked for a v1 pipeline, simplified pipeline, new pipeline format, or when user specifically requests v1 syntax. Do NOT use for v0/standard pipelines (use create-pipeline). Trigger phrases: v1 pipeline, simplified pipeline, new pipeline format, create v1, modern pipeline syntax.
harness · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add harness/harness-skills --skill create-pipeline-v1技能说明
name: create-pipeline-v1 description: >- Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps. Supports CI stages (run, run-test, background), CD stages (service/environment with action steps for K8s, Helm, ECS), approval (stage-level and inline), parallel execution, matrix/for/while strategies, caching, volumes, and templates. Use when asked for a v1 pipeline, simplified pipeline, new pipeline format, or when user specifically requests v1 syntax. Do NOT use for v0/standard pipelines (use create-pipeline). Trigger phrases: v1 pipeline, simplified pipeline, new pipeline format, create v1, modern pipeline syntax. metadata: author: Harness version: 3.1.0 mcp-server: harness-mcp-v2 license: Apache-2.0 compatibility: Requires Harness MCP v2 server (harness-mcp-v2)
Create Pipeline v1
Generate Harness v1 simplified Pipeline YAML and optionally push to Harness via MCP.
Alpha: This skill is currently in internal testing only.
Instructions
- Confirm v1 format - User must specifically want v1 syntax. Default to v0 (
/create-pipeline) if unclear. - Clarify requirements - Pipeline type (CI, CD, or both), language/framework, deployment target
- Consult the spec reference - Use
references/v1-spec-schema.mdfor the complete v1 schema, step types, action catalog, and examples - Select native actions - Always prefer native action and template steps over
run:steps. Consultreferences/native-actions.mdfor the full mapping. Key rules:- Docker build/push → use
template: uses: buildAndPushToDocker/buildAndPushToECR/buildAndPushToGAR(neverrun: docker build && docker push) - K8s deploy → use
action: uses: kubernetes-rolling-deployortemplate: uses: k8sRollingDeployStep(neverrun: kubectl apply) - Helm deploy → use
action: uses: helm-deployortemplate: uses: helmDeployBasicStep(neverrun: helm upgrade --install) - ECS deploy → use
template: uses: ecsBluegreenDeployStep(neverrun: aws ecs update-service) - Terraform → use
template: uses: terraformStep(neverrun: terraform apply) - Security scanning → use native STO templates (
gitleaksStep,banditStep,sbomOrchestrationStep) - Uploads → use
template: uses: uploadArtifactsToS3/uploadArtifactsToGCS(neverrun: aws s3 cp) - Approvals → use
approval: uses: harnessorapproval: uses: jira(never polling scripts) - Ticketing → use
action: uses: jira-create/snow-create(neverrun: curl) - HTTP requests → use
action: uses: httportemplate: uses: httpStep(neverrun: curl) - Use
run:steps only for custom build/test/lint commands with no native equivalent
- Docker build/push → use
- Generate v1 YAML using flat structure,
${{ }}expressions,scriptfield for run steps, andaction/templatesteps for deployments - Optionally create via MCP using
harness_createwith resource_typepipeline
v1 Key Differences from v0
| v0 Syntax | v1 Syntax |
|---|---|
<+variable> expressions | ${{ variable }} expressions |
type: CI / type: Deployment stage types | Flat stages -- no type field |
command: field in Run steps | script: field in run: steps |
Native steps (K8sRollingDeploy, HelmDeploy) | Action steps (action: uses: kubernetes-rolling-deploy) |
failureStrategies: | on-failure: |
HarnessApproval step type | approval: uses: harness (stage-level or inline) |
Deep nesting (spec: execution: steps:) | Flat structure (steps:) |
strategy: matrix: under stage spec | strategy: matrix: directly on stage or step |
Pipeline Structure
pipeline:
name: My Pipeline
repo: # optional: repository config
connector: account.github
name: myorg/my-repo
clone: # optional: clone config
depth: 1
on: # optional: event triggers
- push:
branches: [main]
env: # optional: global env vars
NODE_ENV: production
inputs: # optional: pipeline inputs
branch:
type: string
default: main
stages:
- name: build
steps:
- run:
script: go build
No version:, kind:, or spec: wrapper -- pipeline: is the root key.
Stages
Stages have no type field. Their purpose is determined by their keys.
CI Stage
- name: build
runtime: cloud
platform:
os: linux
arch: arm
cache:
path: node_modules
key: npm.${{ branch }}
steps:
- run:
script: npm ci
Deployment Stage
- name: deploy
service: my-service
environment: staging
steps:
- action:
uses: kubernetes-rolling-deploy
with:
dry-run: false
Approval (stage-level)
- approval:
uses: harness
with:
timeout: 30m
message: "Approve deployment?"
groups: [admins, ops]
min-approvers: 1
Step Types
Run Step
Uses script: field (not command: or run:).
# long syntax
- run:
script: npm test
# short syntax
- run: npm test
# with container
- run:
container: node:18
script: npm test
# with shell and env
- run:
shell: bash
script: |
npm ci
npm test
env:
NODE_ENV: test
# with output variables
- id: build
run:
script: echo "TAG=v1" >> $HARNESS_OUTPUT
output: [TAG]
Run Test Step
- run-test:
container: maven
script: mvn test
report:
type: junit
path: target/surefire-reports/*.xml
splitting:
concurrency: 4
Action Step
Actions replace v0 native steps. See references/v1-spec-schema.md for the full action catalog.
# Kubernetes deploy
- action:
uses: kubernetes-rolling-deploy
with:
dry-run: false
# Helm deploy
- action:
uses: helm-deploy
with:
阅读完整来源 ↗