Going live

What the assistant builds reaches your application's users only once it is live. This page explains how to publish, what is checked first, and how to give up a change that is not live yet.

On this page

Publish from the live app

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

Click it. Kedalia asks for confirmation: “Publish to the live application? Your users will see the changes as soon as publishing ends.” Click “Publish” 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 publication is followed in the test version's conversation, through “Combining with” the application, “Tests”, “Start-up” then “Live”, up to “Your changes have been live since” followed by the time, or the failure. See Test versions. Allow about four minutes. On a phone, a line stuck at the top of the screen follows it while you read the bottom of the conversation.

The steps

At the top of the conversation, publishing moves through “Preparing”, “Testing”, “Starting up” then “Live”. On the application's row in “Applications”, these steps show while publishing runs, then its badge says “Up”. A banner says where it stands: “Publishing: tests running”, then “Publishing: starting up”, always followed by “the site stays up on the previous version”.

In the live app's conversation, after “Publish”, “Publishing” shows the current step, then “The tests passed: the application is starting its new version.”. The line turns into “Published at” followed by the time (and the day, if not today) once the app is live, and the tests' line turns into “Your application is up to date online.”, with “Open” and a button that copies its address. After the very first publication, a line below says “What next? Try it, then say what is missing.”, and “Next change” opens a new conversation. Allow about four minutes. If the tests or the start fail, it turns into “Sent at” followed by the time, without the green check. If the start failed while the tests passed, Kedalia first retries it by itself, twice at most, then “Retry the start-up” puts the same version live again, changing nothing; if it fails again, ask the assistant or write to support.

What is checked first

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

If the tests fail

The live app does not change, and the conversation says so: “The tests failed. The assistant is making them pass by itself, once.”. If it does not manage, click “Make the tests pass”, and the assistant reads the tests' report to fix the application's code, without weakening or removing a test. When the tests passed and it is going live that failed, the conversation says so: “The tests passed, but going live failed…”. The assistant does not repair that by itself: ask it what happened, or write to support.

Abandon the changes

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

  • “Keep the changes” closes the conversation; the change waits, and you will publish it from the next one.
  • “Abandon the changes”, set apart from the other two (on the left on a computer, last on a phone), deletes it for good: a message confirms it (“1 change abandoned.”), the “Publish” button disappears, and the new conversation starts empty.
  • “Cancel” leaves everything as it is.