diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-19 03:18:32 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-19 03:18:32 +0300 |
| commit | f3b2c536778dcd0981134c702d97c6e4047b64d4 (patch) | |
| tree | 46e885f18196164230d95fafd5381b371ffcdaa0 /doc/ci | |
| parent | 2d277754ebd347fd7c98a55d41f6c4de5e9920cc (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci')
| -rw-r--r-- | doc/ci/caching/index.md | 2 | ||||
| -rw-r--r-- | doc/ci/pipelines/schedules.md | 4 | ||||
| -rw-r--r-- | doc/ci/testing/code_coverage.md | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md index d332af418e5..55f18987490 100644 --- a/doc/ci/caching/index.md +++ b/doc/ci/caching/index.md @@ -633,7 +633,7 @@ The next time the pipeline runs, the cache is stored in a different location. You can clear the cache in the GitLab UI: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipelines**. +1. Select **Build > Pipelines**. 1. In the upper-right corner, select **Clear runner caches**. On the next commit, your CI/CD jobs use a new cache. diff --git a/doc/ci/pipelines/schedules.md b/doc/ci/pipelines/schedules.md index 2b85ba495b0..f83868952f5 100644 --- a/doc/ci/pipelines/schedules.md +++ b/doc/ci/pipelines/schedules.md @@ -60,7 +60,7 @@ To trigger a pipeline schedule manually, so that it runs immediately instead of the next scheduled time: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipeline schedules**. +1. Select **Build > Pipeline schedules**. 1. On the right of the list, for the pipeline you want to run, select **Play** (**{play}**). @@ -79,7 +79,7 @@ including [protected environments](../environments/protected_environments.md) an To take ownership of a pipeline created by a different user: 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Build > Pipeline schedules**. +1. Select **Build > Pipeline schedules**. 1. On the right of the list, for the pipeline you want to become owner of, select **Take ownership**. diff --git a/doc/ci/testing/code_coverage.md b/doc/ci/testing/code_coverage.md index 0691c6cfd93..43df79c44f5 100644 --- a/doc/ci/testing/code_coverage.md +++ b/doc/ci/testing/code_coverage.md @@ -76,7 +76,7 @@ To see the evolution of your project code coverage over time, you can view a graph or download a CSV file with this data. 1. On the left sidebar, select **Search or go to** and find your project. -1. On the left sidebar, select **Analyze > Repository analytics**. +1. Select **Analyze > Repository analytics**. The historic data for each job is listed in the dropdown list above the graph. |