内置操作

build 操作

构建操作会创建被跟踪和可观察的 BuildSpec 和 BuildRun 记录：

• 在数据库中创建 BuildSpec（定义要构建的内容）和 BuildRun（执行记录）
• 输出包括 build_id 和 image_digests 映射（服务名称到 SHA256 摘要）
• 这些输出会自动流向依赖的步骤（release 使用 build_id）
• 独立检查构建：eve build show、eve build diagnose、eve build runs、eve build logs

代理步骤

当流水线阶段需要运行 AI 代理任务时，使用 agent 步骤：

pipelines:
  remediation:
    steps:
      - name: analyze
        agent:
          prompt: "Analyze the failure and propose a fix"

标准流水线流程

每个部署流水线都应遵循此模式：

pipelines:
  deploy:
    steps:
      - name: build
        action:
          type: build
          # 创建 BuildSpec + BuildRun，输出 build_id + image_digests
      - name: release
        depends_on: [build]
        action:
          type: release
          # 引用 build_id，从 BuildArtifacts 派生摘要
      - name: deploy
        depends_on: [release]
        action:
          type: deploy
          env_name: staging
          # 使用基于摘要的镜像引用进行不可变部署

提升工作流

在测试环境中构建一次，然后将相同的构建产物提升到预发布/生产环境：

• 构建步骤创建带有产物（镜像摘要）的 BuildRun
• 发布过程携带 build_id 向前传递，确保跨环境使用完全相同的镜像
• 此模式保证您部署的正是您测试过的内容

跟踪流水线执行：

eve job list --phase active
eve job follow <job-id>
eve job result <job-id>

流水线日志与流式传输

实时监控流水线运行：

# 获取运行的快照日志
eve pipeline logs <pipeline> <run-id>

# 实时 SSE 流式传输
eve pipeline logs <pipeline> <run-id> --follow

# 流式传输特定步骤
eve pipeline logs <pipeline> <run-id> --follow --step <name>

失败的步骤会包含失败提示，并在适用时链接到构建诊断信息。

环境部署作为流水线别名

当环境中在清单中配置了 pipeline 时，eve env deploy <env> --ref <sha> 会自动触发该流水线，而不是执行直接部署。

基本用法

# 触发为测试环境配置的流水线
eve env deploy test --ref 0123456789abcdef0123456789abcdef01234567

# 向流水线传递输入
eve env deploy staging --ref 0123456789abcdef0123456789abcdef01234567 --inputs '{"release_id":"rel_xxx"}'

# 绕过流水线，执行直接部署
eve env deploy staging --ref 0123456789abcdef0123456789abcdef01234567 --direct

提升流程示例

# 1. 构建并部署到测试环境
eve env deploy test --ref 0123456789abcdef0123456789abcdef01234567

# 2. 从测试构建中获取发布信息
eve release resolve v1.2.3
# 输出: rel_xxx

# 3. 使用 release_id 提升到预发布环境
eve env deploy staging --ref 0123456789abcdef0123456789abcdef01234567 --inputs '{"release_id":"rel_xxx"}'

关键行为

• 如果设置了 environments.<env>.pipeline，eve env deploy <env> 会触发该流水线
• 使用 --direct 标志来绕过流水线并执行直接部署
• 使用 --inputs '{"key":"value"}' 向流水线运行传递输入
• 默认输入可以通过清单中的 environments.<env>.pipeline_inputs 进行配置
• --ref 标志指定要部署的 git SHA（40 字符的 SHA 或通过 --repo-dir 解析的引用）
• 环境变量和密钥会像往常一样被插值替换

此模式支持提升工作流，您可以在较低环境中构建一次，然后将相同的产物提升到更高的环境中。

工作流

• 在清单的 workflows 下定义工作流。
• 当存在 db_access 时，会遵循其设置（read_only、read_write）。
• 手动调用：
  • eve workflow list
  • eve workflow show <project> <name>
  • eve workflow run <project> <name> --input '{"k":"v"}'（触发后不管）
  • eve workflow invoke <project> <name> --input '{"k":"v"}'（等待结果）
  • eve workflow logs <job-id>
• 调用会创建一个任务；使用常规的任务命令来跟踪它。

工作流提示

通过 hints 控制门控、超时和工具偏好：

workflows:
  remediate:
    hints:
      gates: ["remediate:proj_abc123:staging"]

每周安装数

149

仓库

incept5/eve-skillpacks

首次出现

2026年2月8日

安全审计

Gen Agent Trust HubPassSocketPassSnykPass

安装于

gemini-cli149

codex149

claude-code147

pi53

opencode32

github-copilot32

Built-in Actions

build action

Build actions create BuildSpec and BuildRun records that are tracked and observable:

• Creates BuildSpec (defines what to build) and BuildRun (execution record) in the database
• Outputs include build_id and image_digests map (service name to SHA256 digest)
• These outputs automatically flow to dependent steps (release uses build_id)
• Inspect builds independently: eve build show, eve build diagnose, eve build runs, eve build logs

Agent steps

Use agent steps when a pipeline stage should run an AI agent job:

pipelines:
  remediation:
    steps:
      - name: analyze
        agent:
          prompt: "Analyze the failure and propose a fix"

Canonical pipeline flow

Every deploy pipeline should follow this pattern:

pipelines:
  deploy:
    steps:
      - name: build
        action:
          type: build
          # Creates BuildSpec + BuildRun, outputs build_id + image_digests
      - name: release
        depends_on: [build]
        action:
          type: release
          # References build_id, derives digests from BuildArtifacts
      - name: deploy
        depends_on: [release]
        action:
          type: deploy
          env_name: staging
          # Uses digest-based image refs for immutable deploys

Promotion workflow

Build once in test, then promote the same build artifacts to staging/production:

• The build step creates a BuildRun with artifacts (image digests)
• Releases carry the build_id forward, ensuring identical images across environments
• This pattern guarantees you deploy exactly what you tested

Track pipeline execution:

eve job list --phase active
eve job follow <job-id>
eve job result <job-id>

Pipeline Logs & Streaming

Monitor pipeline runs in real time:

# Snapshot logs for a run
eve pipeline logs <pipeline> <run-id>

# Real-time SSE streaming
eve pipeline logs <pipeline> <run-id> --follow

# Stream specific step
eve pipeline logs <pipeline> <run-id> --follow --step <name>

Failed steps include failure hints and link to build diagnostics when applicable.

Environment Deploy as Pipeline Alias

When an environment has a pipeline configured in the manifest, eve env deploy <env> --ref <sha> automatically triggers that pipeline instead of doing a direct deploy.

Basic usage

# Triggers the configured pipeline for test environment
eve env deploy test --ref 0123456789abcdef0123456789abcdef01234567

# Pass inputs to the pipeline
eve env deploy staging --ref 0123456789abcdef0123456789abcdef01234567 --inputs '{"release_id":"rel_xxx"}'

# Bypass pipeline and do direct deploy
eve env deploy staging --ref 0123456789abcdef0123456789abcdef01234567 --direct

Promotion flow example

# 1. Build and deploy to test environment
eve env deploy test --ref 0123456789abcdef0123456789abcdef01234567

# 2. Get release info from the test build
eve release resolve v1.2.3
# Output: rel_xxx

# 3. Promote to staging using the release_id
eve env deploy staging --ref 0123456789abcdef0123456789abcdef01234567 --inputs '{"release_id":"rel_xxx"}'

Key behaviors

• If environments.<env>.pipeline is set, eve env deploy <env> triggers that pipeline
• Use --direct flag to bypass the pipeline and perform a direct deploy
• Use --inputs '{"key":"value"}' to pass inputs to the pipeline run
• Default inputs can be configured via environments.<env>.pipeline_inputs in the manifest
• The --ref flag specifies which git SHA to deploy (40-character SHA or ref resolved via --repo-dir)
• Environment variables and secrets are interpolated as usual

This pattern enables promotion workflows where you build once in a lower environment and promote the same artifact through higher environments.

Workflows

• Define workflows under workflows in the manifest.
• db_access is honored when present (read_only, read_write).
• Invoke manually:
  • eve workflow list
  • eve workflow show <project> <name>
  • eve workflow run <project> <name> --input '{"k":"v"}' (fire-and-forget)
  • eve workflow invoke <project> <name> --input '{"k":"v"}' (wait for result)
  • eve workflow logs <job-id>
• Invocation creates a job; track it with normal job commands.

Workflow Hints

Control gating, timeouts, and harness preferences via hints:

workflows:
  remediate:
    hints:
      gates: ["remediate:proj_abc123:staging"]

Weekly Installs

149

Repository

incept5/eve-skillpacks

First Seen

Feb 8, 2026

Security Audits

Gen Agent Trust HubPassSocketPassSnykPass

Installed on

gemini-cli149

codex149

claude-code147

pi53

opencode32

github-copilot32