Skip to content

ci(spark): add GitLab CI pipeline (test + build) — Story 7.4 - #2

Draft
WarutC wants to merge 2 commits into
developfrom
feat/7-4-ci-cd-scratch-editor
Draft

ci(spark): add GitLab CI pipeline (test + build) — Story 7.4#2
WarutC wants to merge 2 commits into
developfrom
feat/7-4-ci-cd-scratch-editor

Conversation

@WarutC

@WarutC WarutC commented May 26, 2026

Copy link
Copy Markdown
Owner

Story 7.4 — scratch-editor slice. See parent MR on GitLab for cross-submodule context.

Summary

  • New .gitlab-ci.yml — test + build only, no deploy.
  • test: npm cinpm run lint --workspaces --if-presentnpm test --workspaces.
  • build: npm run build → artifact packages/scratch-gui/build/ (7-day expiry).
  • node:24 image to match .nvmrc; node_modules cached on ref + lockfile.
  • Per-workspace lint via --workspaces --if-present (no top-level lint script today — out of scope for 7.4).

Scope discipline

  • Deploy stays on GitHub Actions (.github/workflows/deploy-uat.yml) until Story 10.3 migrates the image build/push to GitLab Container Registry + ArgoCD.
  • Story 7.5 keeps the GH-Actions deploy workflow alive on Node24 during the transition window (deadline 2026-06-02).
  • This MR does NOT touch .github/workflows/*.

Note

This branch lives on GitHub but the project's CI/CD platform is GitLab (per SCP-2026-05-25). The .gitlab-ci.yml here ships so that when 10.3 retires deploy-uat.yml and the repo migrates fully to GitLab, the test/build pipeline is already in place.

Test plan

  • CI: GitLab pipeline (once repo mirrored / migrated): green on test + build.
  • GitHub Actions: existing workflows still green (no .github/ changes).
  • Local: npm ci && npm test && npm run build (workspace-wide).

🤖 Generated with Claude Code

WarutC and others added 2 commits May 27, 2026 01:32
Story 7.4 — test/build only on GitLab CI; deploy stays on GH Actions until 10.3.

- test: lint + jest via workspaces with --if-present
- build: npm run build, artifact packages/scratch-gui/build (7-day expiry)
- node:24 to match .nvmrc; node_modules cached on ref + lockfile

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…cache)

Per the Story 7.4 code review (2026-05-27), 2 patches in this submodule:

- Add `--if-present` to `npm test --workspaces` so workspaces without
  a `test` script (asset / tooling packages) don't break the pipeline.
  Parity with the lint line above which already uses --if-present.

- Drop the `node_modules/` cache — `npm ci` wipes node_modules on every
  run, so caching it is wasted I/O and risks cross-MR poisoning within
  the same branch. Cache `~/.npm` (npm's download cache) instead via
  `npm_config_cache` env var; `npm ci --prefer-offline` uses it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant