Skip to main content
An application keeps immutable versions of its packaged files, called artifacts. Use release history to identify a version, give it a readable name, and decide which version serves the live URL. Staging saves an artifact without changing the live version. Deployment builds and runs the selected artifact before switching the live URL.

Athena 101 lesson: Publish it as an Application (broader walkthrough)

​
Review and name versions

  1. Open your application and select Deployment.
  2. Review Live Deployment to identify the current release.
  3. Review Version History for versions that have been deployed. Versions also have an ordinal label such as v1 and a separate version ID.
  4. Hover the version’s label and select the pencil (Rename).
  5. Enter a name and select Save name, or press Enter. Clear the name to return to the numbered label.
A name changes how the version appears. It does not change its ID, number, artifact, or deployment target. The numbered label remains visible beside a custom name. Names can contain up to 120 characters. A name can’t look like a version reference, such as v2 or 3, or use the words live, published, production, latest or newest.

​
Stage and deploy changes

  1. In a session with the Applications toolkit, ask Athena to package your changes without deploying them. The stage_application tool saves an immutable version without moving the live URL.
  2. Open Deployment and review the version under Not deployed yet.
  3. Select Deploy this version, then confirm with Deploy.
  4. Wait for deployment and the health check to finish. Confirm the selected version appears under Live Deployment.
If you want to package and deploy in one task, ask Athena to release the application. The release_application tool performs both operations.

How to name a version, deploy a staged version, and roll back to an earlier release

  1. Open Deployment
  2. Check what is live
  3. Name the staged version
  4. Deploy this version
  5. Wait for the health check
  6. Roll back to an earlier release
  7. Check Live Deployment

​
Roll back a release

  1. Find an earlier release in Version History.
  2. Select Roll back to this and confirm with Roll back.
  3. Wait for the selected artifact to rebuild and pass its health check.
  4. Check Live Deployment and open the live application to review the result.
Rollback is not instant. It rebuilds from the saved artifact in a fresh runtime. The existing live app continues serving during the build. The live URL switches after the health check passes. If that check fails, the published version stays unchanged.

​
Limits

You need edit permission to rename or deploy versions. New builds, deployment, and rollback also require application deployment to be available in your environment. You can read existing release history while new releases are paused.