Build failed

The build stage runs entirely in your GitHub Actions runner — dependency install, compile, and tests. Nothing in your AWS account is touched by this stage, so there is no infrastructure state to inspect or clean up.

Where to look

1. On the failed attempt in ScaleBop, open the View GitHub run link for the run.
2. Open the failed build job (the first job in the generated workflow).
3. Expand the failing step — commonly Build application, Run tests, or the dependency install.
4. Copy 10–30 lines around the first clear error: a compiler message, a missing module, a failing test, or a non-zero exit from the install.

Common causes

• Dependency install — a npm install / npm ci (or equivalent) failure: a missing lockfile entry, a registry/auth issue, or a platform mismatch.
• Compile or type error — the build command exits non-zero.
• Tests — a test suite failing in the runner environment.

These are ordinary application bugs; the fix is the same fix you would make running the build locally.

Fix and retry

Fix the error in your repository, push, and run the deploy workflow again (from ScaleBop’s Pipeline page or from GitHub Actions). Once the build passes, the workflow continues on to the deploy stage (then publish for static sites) and health-check.

If the build passes locally but fails in the runner, re-read the excerpt: runner failures are usually environment-specific (a missing file the build expects, a dependency platform mismatch, or a timeout on a slow install).