Going live

Deploy from the live app

In the live app's conversation, an executed plan or an applied correction ends with “Change saved, not deployed yet”: nothing has changed for the users. The “Deploy (1)” button then appears under the message box; the number in brackets counts the saved changes that are waiting.

Click it. Kedalia asks for confirmation: “Update the live application? The saved changes go live: the application's users see them as soon as the deployment ends.” Click “Deploy” again, or “Cancel” to wait.

From a test version

A test version has no such button: when the assistant is done, the change is installed on the test version by itself. To bring it into the live app, click “Publish”: the conversation stays on screen, read-only, and follows the live app's update through the steps below.

The steps

Above the conversation, and on the application's card in “Applications”, the deployment moves through “Preparing”, “Testing”, “Deploying” then “Live”. A banner says where it stands: “New deployment: tests running”, then “building and starting”, always followed by “the site stays up on the previous version”.

In the conversation, “Changes delivered” shows the current step, then “The tests passed: the deployment was triggered.”. Allow about two minutes.

What is checked first

Two checks run before going live. The assistant first checks its own work: the conversation shows “Checking the change before delivering it…”, and its summary says whether the checks passed. Then, at the “Testing” step, the application's automatic tests run, along with a search for secrets (passwords, access keys) in what was changed. Nothing goes live if the tests fail.

If the checks fail

The live app does not change, and the conversation says so: “The checks failed. The assistant is fixing them by itself, once.”. If it does not manage, the conversation shows “The checks failed and could not be fixed automatically.”: click “Fix the failed checks”, and the assistant reads the checks' report to fix the application.

Abandon the changes

A change that is saved but not deployed yet can be abandoned. Click “New conversation”: Kedalia reminds you that a saved change is not deployed yet, and offers three buttons.

• “Keep the changes” closes the conversation; the change waits, and you will deploy it from the next one.
• “Abandon the changes” deletes it for good: the “Deploy” button disappears, and the new conversation starts empty.
• “Cancel” leaves everything as it is.