// Observability

Deployment History & Insights

What shipped, when, where and who deployed it.

Jaws Deploy keeps a record of every release and deployment: what it contained, where it ran, who started it and the full log. You can answer questions about last year's deployments without searching CI logs.

What each deployment records

Every deployment is stored in the database with the rest of your workspace, for the life of the account. Open any past deployment to see what it did.

Recorded for every deployment

Release and packages The release version, its release notes and the package versions it was created with.

Variables The variables and scoped values the release was created with. Later edits to the project don't change them. Secret values appear as **** in logs.

Full log The log you watched live, grouped by step and target, with warning and error counts.

Who, where and when Who started the deployment, the environment, the machines and cloud targets it ran on, and its start and end times.

Finding a past deployment

The dashboard shows each project's recent deployments, with charts of deployment duration and activity over up to 90 days. Each release lists the environments it was deployed to and when.

To check whether a fix reached Production before a given date, find the release that contains it and look at its Production deployments.

History through the REST API

The List deployments endpoint returns the same records for your own reports and dashboards. Scope it to a workspace, project or release, filter by environment, and use changedSince to fetch only what changed since your last call.

GET /api/deployment/list?projectId=<project id>&environmentNames=Production&max=100
Authorization: Basic <base64(serviceAccountId:apiKey)>

Rolling back

Old releases keep their packages, variables and steps, so rolling back means deploying the previous release again. That deployment is recorded like any other, and the history shows both the failed deployment and the rollback.