Skip to main content

Archive Build Runs on Test Observability

Learn how to archive build runs to declutter your test run data.

What is the use case for archiving build runs?

Over time, the build and test run data in your Test Observability account could become cluttered and noisy due to several reasons. This can result in the rich insights and testing metrics provided by Test Observability becoming unreliable or skewed, providing an inaccurate state of testing in your organization.

Archiving build runs is a feature that allows you to clean up your testing activity so it doesn’t pollute your testing metrics.

Some examples of when you might want to archive build runs from your Test Observability project are:

  • Issues with network, environment, or setup, causing entire builds to fail.
  • Builds triggered by accident.
  • Builds triggered as pipeline test jobs.

If you archive a build run, it becomes read-only. You can’t trigger any action on that build run anymore. Also, Test Observability recalculates Smart Tags and other test metrics, excluding the tests in archived build runs.

How to archive build runs?

Warning: Archiving build runs is permanent and cannot be undone.

Follow these steps to archive build runs:

  1. You can trigger archiving a build run in two ways:
    • From Build Runs, navigate to the builds you want to archive, select the checkboxes next to it, and click Archive. Click kebab menu and click the Archive button
    • From Build Insights, click the kebab menu and click the Archive button. Select the builds and click the Archive button
  2. Read through the instructions in the pop-up and type Archive in the textbox. Type 'Archive' in the text box
  3. Click Archive build run Click the 'Archive build run' button
    A message ‘Build archive successful’ is displayed after archiving the build run.
    Build run archived success message screenshot

What happens when you archive a build run?

Test Observability removes archived build runs from the default view inside Build Runs. Archived build runs become non-editable. Test Observability also recalculates all the Smart Tags, metrics, and charts after you archive a build run.

The following table summarizes how the features and metrics in Test Observability handle archived build runs.

Feature/Metric Effect after Archiving
Re-run Disabled
Muting Disabled
Flakiness Smart Tag Recalculated after excluding tests from archived build runs.
Always Failing Smart Tag Recalculated after excluding tests from archived build runs.
New Failures Smart Tag Recalculated after excluding tests from archived build runs.
Performance Anomalies Smart Tag Recalculated after excluding tests from archived build runs.
Reporting bugs on Jira Active
Downloading reports Active
View Build Insights and Test Listing Active
Metrics on the Tests Health Dashboard Recalculated after excluding tests from archived build runs.
Metrics on the Testing Trends Dashboard Recalculated after excluding tests from archived build runs.
Metrics on the Unique Errors Dashboard Recalculated after excluding tests from archived build runs.

How to view an archived build run?

To view an archived build run:

  1. From Build Runs, click the Filters button on the top-right corner.
    Click the filters button on the build runs dashboard
  2. Switch on the Select archived builds only toggle button.
    Click the toggle button to show archived build runs only
  3. Click Apply.
    Click the Apply button to show archived build runs only
    Build Runs displays all the archived builds. Archived builds are prepended with the text [Archived] before the build name.
    Archived builds runs can be seen with the text 'Archived' before the build name

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better

Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Download Copy