From dcc92daaab75e99599fc330197f8e751dd4fdccf Mon Sep 17 00:00:00 2001
From: Manuel Grabowski <mgrabowski@gitlab.com>
Date: Sun, 23 Jul 2023 07:31:07 +0000
Subject: [PATCH] Clarify what job archival actually entails

---
 doc/administration/settings/continuous_integration.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/doc/administration/settings/continuous_integration.md b/doc/administration/settings/continuous_integration.md
index eaa240d4c9669..6abef613be006 100644
--- a/doc/administration/settings/continuous_integration.md
+++ b/doc/administration/settings/continuous_integration.md
@@ -172,9 +172,12 @@ All application settings have a [customizable cache expiry interval](../../admin
 
 ## Archive jobs
 
-Archiving jobs is useful for reducing the CI/CD footprint on the system by removing some
-of the capabilities of the jobs (metadata stored in the database needed to run the job),
-but persisting the traces and artifacts for auditing purposes.
+You can archive old jobs to prevent them from being re-run individually. Archived jobs
+display a lock icon (**{lock}**) and **This job is archived** at the top of the job log.
+
+Future work is planned to reduce the CI/CD footprint on the system for archived jobs
+by removing metadata stored in the database needed to run the job. See the [CI/CD data time decay](../../architecture/blueprints/ci_data_decay/index.md)
+blueprint for more details.
 
 To set the duration for which the jobs are considered as old and expired:
 
-- 
GitLab