Deployment in Progress

Once you have successfully triggered a deployment, we want to show you as much detail as possible about its progress. This page serves as a guide to lead you through the different segments of the Deployment Detail Page.

The Deployment Detail Page consists of three complementary sections:

Progress Details

The main purpose of this section is to show the different stages of the deployment from a timeline perspective.

The stages are:

Code Checkout: In the first step, our application checks out the Git reference of the Storefront Application code. This ensures that our deployment processes are working with the correct codebase that is targeted for deployment.
Build Step: The next step is crucial for the deployment, as our application takes the Storefront Application code and transforms it into a deployable artifact. This includes resolving dependencies and compiling the code for execution.
Upload Assets: Once the application has been built and packaged, this stage involves uploading static client assets to the Cloudflare Content Delivery Network.
Deployment: This is the final stage where we launch the Storefront Application, putting it into action, so you can use it.

On every stage, detailed timestamp information is always available, showing the date, time, and duration of that specific step.

General Information

This section provides general information on the application. It consists of the following fields:

Domain: Shows SCAYLE-generated domain, for an easy preview of your application.
Environment: Shows the environment from which the deployment was triggered.
Status: Shows the status of the deployment.
Source: Shows the Git branch or tag from which the deployment was triggered.
Duration: Shows the duration of the deployment stage.

Possible statuses include:

Building: Currently in the process of building the application.
Running: The deployment is rolling out.
Succeeded: The deployment finished successfully.
Failed: Something went wrong with the deployment.
Canceled: The deployment got canceled by the user.

In certain cases, when the process of deploying the application hasn't started yet, it is also possible to stop the deployment. Since this is a delicate action, we will always ask you to double-confirm the action of stopping the deployment.

Build Logs

The build logs are detailed, chronological records of every action and event that occurs during your application's build process. They provide invaluable insights into the health and progress of your build. They are essential for diagnosing failures, helping developers quickly debug the issue that caused a build to fail.

Our build logs consist of the timestamp and the log message, presented in chronological order, showing the oldest entries first.