Deployments

A deploy builds the service’s latest commit and runs it through a pipeline. When every step passes, that commit becomes the Live version.

​

Deploy a service

Click Deploy in the service header. The header shows Deploying and the progress, such as Deploying · 5/17, while the pipeline runs. You can keep working. Only one deploy runs at a time, so starting another while one is running shows the existing one. Each deploy builds Head, the latest commit. If you edited files, save them first. Changes you haven’t saved aren’t deployed. A failed deploy never replaces the live version. The service keeps running the last good commit.

​

Deployment history

Open the Deployments tab. The number next to the tab is the count of deploys for this service. The list on the left groups deploys by day and shows, for each one:

• The commit message and the short commit hash.
• Who started it and the time.
• The trigger, such as Manual.
• The duration.
• A Live label on the deploy that’s running now.

At the top of the list, a summary reads like “14 deploys · median 2m 15s”. Use All and Failed to filter the list. Select a deploy to see its details on the right.

​

Deploy states

A successful deploy shows how long it was live and how it compares to the median, for example “16.3s faster than the median”.

​

The deploy pipeline

Every deploy runs the same steps, grouped into four stages. A successful run shows 17 passed. Some points about specific steps:

• Load environment variables reads the environment’s variables and secrets for this deploy.
• Register API and Reconcile GraphQL schema add the service’s operations to your project’s API. After a deploy, they appear in the GraphQL API Explorer.
• If a step finishes with a warning, the deploy continues. Open the logs for that step to read the details.

If a step after a failure doesn’t run, it shows Skipped.

​

When a deploy fails

A failed deploy shows the stage and step that failed, for example Failed at Build image · step 5 of 17, and a red progress bar. Below it, Archie reminds you: “Nothing changed for your users: a2afeb1 is still live.” To find the cause:

1. Select the failed deploy in the list.
2. Find the red step in the Pipeline and read its message. For a build failure, it reads “This step failed. Open the environment logs for details.”
3. Click View logs to read the logs for the deploy. See also Logs.
4. Fix the code in the Code tab and click Save.
5. Click Deploy.

If the failure looks temporary, click Retry deploy on the failed deploy to run it again without changing anything.

​

The GraphQL schema warning

If the Reconcile GraphQL schema step can’t finish, Archie still deploys the service. The service answers requests at its endpoint, but new operations may be missing from the API and from the API Explorer. Redeploying usually fixes it.

​

Redeploy an earlier commit

To go back to a version that worked, open an earlier successful deploy and click Redeploy this commit. Archie asks you to confirm. Archie builds and deploys that commit again. When it’s healthy, it replaces the live version. The commit itself isn’t rewritten: Head still points at your latest commit and shows Undeployed changes until you deploy it.

​

Deploys and environments

Each deploy lists the Environment it ran in, such as master. The service list and its deploy history are scoped to the environment selected in the Backend Console. If a service doesn’t appear after you switch environments, it belongs to another one. See Environments.

​

FAQ