From fab00cd7efb84b369dfb45cabb797f7feace4b66 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Wed, 31 May 2023 15:07:20 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/ci/pipelines/pipeline_artifacts.md | 29 +++++++-------------------- doc/ci/runners/saas/linux_saas_runner.md | 5 +++-- doc/ci/testing/test_coverage_visualization.md | 7 ++++--- doc/ci/yaml/index.md | 4 ---- 4 files changed, 14 insertions(+), 31 deletions(-) (limited to 'doc/ci') diff --git a/doc/ci/pipelines/pipeline_artifacts.md b/doc/ci/pipelines/pipeline_artifacts.md index d8db79a54dc..79435c0276d 100644 --- a/doc/ci/pipelines/pipeline_artifacts.md +++ b/doc/ci/pipelines/pipeline_artifacts.md @@ -2,28 +2,13 @@ stage: Verify group: Pipeline Security info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments +redirect_to: '../testing/test_coverage_visualization.md' +remove_date: '2023-08-31' --- -# Pipeline artifacts **(FREE)** +This document was moved to [another location](../testing/test_coverage_visualization.md). -Pipeline artifacts are files created by GitLab after a pipeline finishes. Pipeline artifacts are -different to [job artifacts](../jobs/job_artifacts.md) because they are not explicitly managed by -`.gitlab-ci.yml` definitions. - -Pipeline artifacts are used by the [test coverage visualization feature](../testing/test_coverage_visualization.md) -to collect coverage information. - -## Storage - -Pipeline artifacts are saved to disk or object storage. They count towards a project's [storage usage quota](../../user/usage_quotas.md#storage-usage-quota). -The **Artifacts** on the Usage Quotas page is the sum of all job artifacts and pipeline artifacts. - -## When pipeline artifacts are deleted - -Pipeline artifacts from: - -- The latest pipeline are kept forever. -- Pipelines superseded by a newer pipeline are deleted seven days after their creation date. - -It can take up to two days for GitLab to delete pipeline artifacts from when they are due to be -deleted. + + + + diff --git a/doc/ci/runners/saas/linux_saas_runner.md b/doc/ci/runners/saas/linux_saas_runner.md index 055cf651067..f596d4da8c5 100644 --- a/doc/ci/runners/saas/linux_saas_runner.md +++ b/doc/ci/runners/saas/linux_saas_runner.md @@ -98,9 +98,10 @@ Below are the settings for SaaS runners on Linux. and [#4070](https://gitlab.com/gitlab-com/gl-infra/reliability/-/issues/4070). NOTE: -SaaS runner instances are provisioned with a 25 GB storage volume. The underlying disk space of the storage volume +Typical SaaS runner instances are provisioned with a 25 GB storage volume. GPU-enabled runners +are provisioned with a 50 GB storage volume. The underlying disk space of the storage volume is shared by the operating system, the Docker image, and a copy of your cloned repository. -This means that the available free disk space that your jobs can use is **less than 25 GB**. +This means that the available free disk space that your jobs can use is **less than 25 (or 50) GB**. diff --git a/doc/ci/testing/test_coverage_visualization.md b/doc/ci/testing/test_coverage_visualization.md index 31d1b7f3337..2fcd1ecfad2 100644 --- a/doc/ci/testing/test_coverage_visualization.md +++ b/doc/ci/testing/test_coverage_visualization.md @@ -73,10 +73,11 @@ a [blocking manual job](../jobs/job_control.md#types-of-manual-jobs), the pipeline waits for the manual job before continuing and is not considered complete. The visualization cannot be displayed if the blocking manual job did not run. -### Artifact expiration +### Data expiration -By default, the [pipeline artifact](../pipelines/pipeline_artifacts.md#storage) used -to draw the visualization on the merge request expires **one week** after creation. +> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/321323) in GitLab 13.12, the latest data is kept regardless of expiry time. + +By default, the data used to draw the visualization on the merge request expires **one week** after creation. ### Coverage report from child pipeline diff --git a/doc/ci/yaml/index.md b/doc/ci/yaml/index.md index 2cabb4bbaab..6e4effe4298 100644 --- a/doc/ci/yaml/index.md +++ b/doc/ci/yaml/index.md @@ -837,7 +837,6 @@ subdirectories of `binaries/`. > - [Made default behavior](https://gitlab.com/gitlab-org/gitlab/-/issues/229936) in GitLab 13.4. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241026) in GitLab 13.8, keeping latest job artifacts can be disabled at the project level. > - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/276583) in GitLab 13.9, keeping latest job artifacts can be disabled instance-wide. -> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/321323) in GitLab 13.12, the latest pipeline artifacts are kept regardless of expiry time. Use `expire_in` to specify how long [job artifacts](../jobs/job_artifacts.md) are stored before they expire and are deleted. The `expire_in` setting does not affect: @@ -845,9 +844,6 @@ they expire and are deleted. The `expire_in` setting does not affect: - Artifacts from the latest job, unless keeping the latest job artifacts is disabled [at the project level](../jobs/job_artifacts.md#keep-artifacts-from-most-recent-successful-jobs). or [instance-wide](../../user/admin_area/settings/continuous_integration.md#keep-the-latest-artifacts-for-all-jobs-in-the-latest-successful-pipelines). -- [Pipeline artifacts](../pipelines/pipeline_artifacts.md). You can't specify an expiration date for - pipeline artifacts. See [When pipeline artifacts are deleted](../pipelines/pipeline_artifacts.md#when-pipeline-artifacts-are-deleted) - for more information. After their expiry, artifacts are deleted hourly by default (using a cron job), and are not accessible anymore. -- cgit v1.2.3