Skip to content

Use run script in our CI instead of calling lower level script directly #3230

@infomiho

Description

@infomiho

We have a our run script which codifies common tasks that we need to do while developing the Wasp compiler e.g. build TS packages, run e2e tests and similar.

In our CI, we repeat some of the common tasks from the dev workflow e.g. run unit tests, build TS packages and similar.

We don't' use the run script in the CI, but call the lower level commands directly. We should use run as much a possible which would mean we run things locally and in the CI the same way.

To paint a picture:

# dev

call run -> call cabal test -> tests run

# CI
call cabal test -> tests run

Based on: #2989 (comment) and internally Discord discussion: https://discord.com/channels/686873244791210014/1351908377533354025/1405530072898863194

Metadata

Metadata

Assignees

No one assigned

    Labels

    ciContinuous integrationfaster wasp devImprovements that make developing Wasp itself faster and easier.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions