chainplot/.github/workflows/ci.yml at main · chainstacklabs/chainplot · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  test:
    name: Build & Test
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7

      - uses: pnpm/action-setup@v6
        with:
          version: 11.24.0

      - uses: actions/setup-node@v7
        with:
          node-version: 22
          cache: pnpm

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

      # The viewer is a separate project with its own lockfile. Typecheck it
      # explicitly: `vite build` does not, so a type error here would
      # otherwise ship in the bundle every release embeds.
      - name: Install viewer dependencies
        run: pnpm --dir viewer install --frozen-lockfile

      - name: Typecheck viewer
        run: pnpm --dir viewer run typecheck

      - name: Build CLI and viewer
        run: pnpm build

      - name: Run tests
        run: pnpm vitest run

  template-smoke:
    name: Scaffolded template runs
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7

      - uses: pnpm/action-setup@v6
        with:
          version: 11.24.0

      - uses: actions/setup-node@v7
        with:
          node-version: 22
          cache: pnpm

      - name: Install dependencies
        run: |
          pnpm install --frozen-lockfile
          pnpm --dir viewer install --frozen-lockfile

      - name: Build CLI and viewer
        run: pnpm build

      # The producer image is the CLI plus rindexer, which ships linux/amd64
      # only. Every step below is what a user does from the template README;
      # each of them was broken at some point and none was covered by a test.
      - name: Build the producer image
        run: |
          docker build --platform linux/amd64 -t chainplot:local \
            -f docker/producer.Dockerfile .

      - name: Scaffold the template
        run: |
          node dist/cli/main.js init --template ingest-transfers \
            --output "$RUNNER_TEMP/proj" --json

      # No RPC is needed to prove the stack comes up and the CLI is reachable.
      - name: Bring the stack up and drive the CLI
        working-directory: ${{ runner.temp }}/proj
        run: |
          printf 'RPC_URL=http://127.0.0.1:1\n' > .env
          docker compose up -d
          docker compose ps
          docker compose exec -T producer chainplot capabilities --json
          docker compose exec -T producer chainplot validate --json

      # The container writes into the bind-mounted project as its owner, not as
      # root, so a build run inside it leaves files the host user can read and
      # delete without sudo. The fixture template builds offline.
      - name: Files the container writes belong to the host user
        working-directory: ${{ runner.temp }}/proj
        run: |
          docker compose exec -T producer chainplot init \
            --template fixture-transfers --output /workspace/fx --json
          docker compose exec -T -w /workspace/fx producer chainplot build --json
          test -O fx/dist/releases/local/release.json
          rm -rf fx

      - name: Tear down
        if: always()
        working-directory: ${{ runner.temp }}/proj
        run: docker compose down -v