Deployment in Progress

After you trigger a deployment, the Deployment Details page becomes the place to watch it unfold in real time - from Code Checkout through Build to Deployment. This page explains each stage, the statuses you'll see along the way, and how to stop a deployment if needed.

The Deployment Details page itself is described in Deployment Overview. This page focuses specifically on what happens during a deployment.

Pipeline stages

Every deployment moves through four stages, shown as a vertical timeline on the Deployment Details page:

1. Code Checkout - clones the Git reference (branch, tag, or commit) of your Storefront Application code. This ensures the deployment uses the correct codebase.
2. Build - transforms your application code into a deployable artifact: installing dependencies, compiling, and packaging. See Application Build for build configuration details, including Node.js version handling.
3. Upload Assets - uploads static client assets to the Cloudflare CDN for edge delivery.
4. Deployment - launches the Storefront Application and routes traffic to it.

Each stage shows its start time, end time, and duration, so you can spot bottlenecks if a deployment runs longer than expected.

Build configuration

The Build stage transforms your Storefront Application code into a deployable artifact. To simplify the process and remove the need to manage complex build configurations, SCAYLE uses a standardized container image in the background you don't need to provide a Dockerfile in your repository.

The only required configuration for the build process is specifying a Node.js version constraint in the engines.node field of your package.json. This tells the platform which Node.js version to use for the build.

Node.js Version Selection

The platform supports all current Node.js Long Term Support (LTS) versions. When a build is triggered, the version constraint in your package.json is read and the most recent compatible Node.js image is selected.

For example, the following configuration in package.json:

json

json

Copy

This constraint indicates that your application requires a Node.js version of 22.15.0 or higher. The platform then selects the most up-to-date Node.js 22 image that satisfies the requirement, ensuring your build benefits from the latest security patches and performance improvements within that major version.

This approach gives you the flexibility to define your application's requirements while SCAYLE handles image selection and maintenance.

Node.js 20 Deprecation

For Node 22:

json

Copy

For Node 24:

json

Copy

Deployment statuses

The deployment status reflects which phase the deployment is in:

• Pending - the deployment is queued and waiting to start.
• Running - the build succeeded and the deployment is rolling out.
• Succeeded - the deployment finished successfully and is now live.
• Failed - something went wrong during the build or deployment. Check Build Logs for details.
• Canceled - the deployment was stopped manually.
• Build Expired - the application build was deleted (e.g., due to age or storage limits).

Cancelling a deployment

You can cancel a deployment that hasn't started running yet using the Cancel Deployment button on the Deployment Details page. This is available while the deployment is in the Pending state (queued but not yet started). Once Code Checkout begins, the option is no longer available.

A cancelled deployment does not affect your currently active deployment — the previous successful version remains live until a new deployment succeeds and replaces it.

Build Logs

The Build Logs tab on the Deployment Details page shows a chronological record of every action during the build process- oldest entries first. Each entry includes a timestamp and a log message.