CI Pipeline — Meriadoc Examples

Lint, test, and build on every push — a drop-in replacement for a Jenkinsfile or a basic GitHub Actions workflow.

A standard lint → test → build pipeline, composed as a job from three individual tasks. Run each step on its own while debugging (meriadoc task lint), or the whole thing as a unit in CI (meriadoc job ci). Because the same spec drives both local runs and CI, there’s no drift between “what runs on your machine” and “what runs on the build server” — point your CI step at meriadoc job ci instead of duplicating the lint/test/build commands in a separate CI config.

version: v1

tasks:
  lint:
    description: "Run ESLint"
    cmds:
      - npm run lint

  test:
    description: "Run the test suite"
    cmds:
      - npm test

  build:
    description: "Build for production"
    cmds:
      - npm run build

jobs:
  ci:
    description: "Full CI pipeline: lint, test, build"
    tasks:
      - lint
      - test
      - build
    on_failure:
      continue: false
      cmds:
        - echo "CI failed — check the logs above."

Run it:

meriadoc job ci