eve-pipelines-workflows

Eve Pipelines and Workflows

Use these patterns to automate build and deploy actions and invoke workflow jobs.

Pipelines (v2 steps)

• Define pipelines under pipelines in .eve/manifest.yaml.
• Steps can be action, script, or agent.
• Use depends_on to control ordering.
• Built-in actions include build, release, deploy, run, job, create-pr.
• Run manually:
  • eve pipeline list
  • eve pipeline show <project> <name>
  • eve pipeline run <name> --ref <sha> --env <env> --repo-dir ./my-app
• Trigger blocks exist in the manifest; GitHub and Slack webhooks can create pipeline runs.

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: