1. Docs
  2. Resources
  3. Deploys & Repos
  4. Versions, history and deploy detail

Versions, history and deploy detail

The Overview tab shows what runs where now, every deploy in a period, and, for one deploy, what changed and which pipeline runs tested it.

4 min read Updated CustomersAdmins

In short

On this page you can

  • Read the commit, version and age of each service in each environment.
  • See at a glance which deploys are Tested, broken, running or Not tested.
  • Filter the Deploy history by environment, service and the last 7 to 365 days.
  • Open a deploy for its previous version, commits, changed files and pipeline runs.

How to use it

  1. Look for amber Not tested cells in Currently running versions.
  2. Click the cell to open the deploy detail.
  3. Read Change from previous version and the Commits.
  4. Under Tests after deploy, click a run to open its report.

Currently running versions#

One row per repository (service name in bold, repository name below), one column per environment. The columns are always DEV, TEST and PRP, plus every environment that appears in a repository’s mapping or in a deploy record.

What a cell shows#

  • Short commit (the first 7 characters of the SHA), then the version if CI sent one, then the age, for example a1b2c3d v2.14.0 · 3 h ago.
  • Test state chip for the last successful deploy in that environment. How each state is decided.
  • A line below when the newest record is not a success: “Deploy in progress”, or “Last deploy failed · sha”. The chip above still describes the version that is really running.
Chip or textColourMeaning
Tested · 18/20GreenThe newest pipeline run after this deploy had no failed test cases. 18 of its 20 test cases passed; the other 2 ended with another result, such as stopped.
2 broken · 18/20RedThe newest run after this deploy has 2 failed test cases.
Test running · pipelineBlueThe newest run is still running.
Not testedAmberNo pipeline ran in this environment since the deploy.
Not tested · 3 deploysAmberThe last 3 successful deploys in a row were all untested (counted up to 5).
No pipeline environmentGreyThe environment is your own (for example STAGING). Pipelines do not run there, so no test state exists.
No deploy yet—The environment is mapped, but no deploy arrived.
Not mapped—The environment is switched off in this repository’s mapping and nothing was deployed there.

Click any cell with a deploy to open its detail. The grid scrolls sideways when there are many environments.

Tested means “a pipeline ran in this environment”

The match is by environment and time, for the whole project. A TEST pipeline that only covers the web app also counts as testing the api deployed to TEST at the same time. Name your pipelines so the run list tells you what they covered. Details in the tested-after window.

Deploy history#

Every deploy record of the project, newest first, 20 at a time. Load more adds the next 20.

FilterOptions
EnvironmentAll or one environment column.
ServiceAll or one repository’s service name.
PeriodLast 7 days, Last 30 days (default), Last 90 days, Last 365 days.
ColumnShows
TimeDay, month and time of the deploy.
Service, EnvironmentWhere it went.
VersionShort commit (blue), version, and for a successful deploy with a predecessor ← 9f8e7d6 · 5 commits.
ByThe actor CI sent, or —.
DeploySucceeded, Failed, In progress or Cancelled.
Tested afterThe test state chip for successful deploys; — for the others.

With no records in the period: “No deploys in this period.” Click a row (or focus it and press Enter) to open the detail. Deploys of a deleted repository stay in the history.

Deploy detail#

A side panel. The header shows repository · environment, the short commit and version, then the status chip, time, branch, actor and Open CI run when CI sent a build URL.

SectionWhat you see
Change from previous version9f8e7d6 → a1b2c3d, the number of commits and files, and Open comparison on your Git provider. The first deploy in an environment shows “First recorded deploy in this environment.” A failed or cancelled deploy shows “No diff for an unsuccessful deploy.”
Tests after deployOnly for successful deploys. “Pipeline runs in this environment until the next deploy”, newest first, up to 10. Each run shows its pipeline name, start time and passed/total with the broken count. Click a run to open it in Report.
Commits (n)Newest first: short SHA (a link to the commit), first line of the message, author. Up to 100; more shows “Showing the first 100 commits.” The refresh icon Read commits again asks the provider again.
Show changed files (n)Status (added, modified, removed, renamed), path and +added −removed lines where the provider gives them. Up to 300 files.
NoteThe description CI sent.

When commits are missing#

  • “Commit list is shown when the repository is connected with a token.” The repository uses Deploy notification only or provider Other. Add a token.
  • “This is the first recorded deploy for this environment; there is no previous version to compare.”
  • “No commits between these versions.” A redeploy of the same commit.
  • An amber box with the provider’s reason, for example a rejected token. See connection errors.

SmartestQA reads the commits when the deploy arrives and again the first time you open a deploy that has none yet, then keeps them. Adding a token later fills older deploys the next time you open them.

Refresh#

The page does not update by itself. Click the Refresh icon (top right) after a deploy or a pipeline run; it reloads the cards, the grid and the history and shows Refreshed. If loading fails you see “Could not load.” and no confirmation.

If something goes wrong#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai