Add latest changes from gitlab-org/gitlab@master

doc/administration/repository_checks.md

@@ -1,6 +1,6 @@
 ---
 stage: Create
-group: Editor
+group: Gitaly
 info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments"
 type: reference
 ---
@@ -44,3 +44,23 @@ in the [`repocheck.log` file](logs.md#repochecklog) on disk:
 If the periodic repository check causes false alarms, you can clear all repository check states by
 going to **Admin Area > Settings > Repository**
 (`/admin/application_settings/repository`) and clicking **Clear all repository checks**.
+
+## Run a check manually
+
+[`git fsck`](https://git-scm.com/docs/git-fsck) is a read-only check that you can run
+manually against the repository on the [Gitaly server](gitaly/index.md).
+
+- For Omnibus GitLab installations, repositories are stored by default in
+  `/var/opt/gitlab/git-data/repositories`.
+- [Identify the subdirectory that contains the repository](repository_storage_types.md#from-project-name-to-hashed-path)
+   that you need to check.
+
+To run a check (for example):
+
+```shell
+sudo /opt/gitlab/embedded/bin/git -C /var/opt/gitlab/git-data/repositories/@hashed/0b/91/0b91...f9.git fsck
+```
+
+You can also run [Rake tasks](raketasks/check.md#repository-integrity) for checking Git
+repositories, which can be used to run `git fsck` against all repositories and generate
+repository checksums, as a way to compare repositories on different servers.

doc/ci/pipelines/index.md

@@ -6,9 +6,7 @@ disqus_identifier: 'https://docs.gitlab.com/ee/ci/pipelines.html'
 type: reference
 ---
 
-# CI/CD pipelines
-
-> Introduced in GitLab 8.8.
+# CI/CD pipelines **(FREE)**
 
 NOTE:
 Watch the
@@ -199,8 +197,6 @@ For each `var` or `file_var`, a key and value are required.
 
 ### Add manual interaction to your pipeline
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/7931) in GitLab 8.15.
-
 Manual actions, configured using the [`when:manual`](../yaml/README.md#whenmanual) keyword,
 allow you to require manual interaction before moving forward in the pipeline.
 
@@ -324,8 +320,6 @@ runners do not use regular runners, they must be tagged accordingly.
 
 ## Visualize pipelines
 
-> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/5742) in GitLab 8.11.
-
 Pipelines can be complex structures with many sequential and parallel jobs.
 
 To make it easier to understand the flow of a pipeline, GitLab has pipeline graphs for viewing pipelines

doc/user/application_security/sast/index.md

@@ -375,8 +375,6 @@ If all dependencies are present, the `COMPILE=false` CI/CD variable can be provi
 analyzer and compilation is skipped:
 
 ```yaml
-image: maven:3.6-jdk-8-alpine
-
 stages:
   - build
   - test
@@ -385,6 +383,7 @@ include:
   - template: Security/SAST.gitlab-ci.yml
 
 build:
+  image: maven:3.6-jdk-8-slim
   stage: build
   script:
     - mvn package -Dmaven.repo.local=./.m2/repository

doc/user/project/merge_requests/test_coverage_visualization.md

@@ -146,7 +146,7 @@ coverage-jdk11:
   # The `visualize` stage does not exist by default.
   # Please define it first, or chose an existing stage like `deploy`.
   stage: visualize
-  image: haynes/jacoco2cobertura:1.0.4
+  image: registry.gitlab.com/haynes/jacoco2cobertura:1.0.7
   script:
     # convert report from jacoco to cobertura
     - 'python /opt/cover2cover.py target/site/jacoco/jacoco.xml src/main/java > target/site/cobertura.xml'
@@ -186,7 +186,7 @@ coverage-jdk11:
   # The `visualize` stage does not exist by default.
   # Please define it first, or chose an existing stage like `deploy`.
   stage: visualize
-  image: haynes/jacoco2cobertura:1.0.4
+  image: registry.gitlab.com/haynes/jacoco2cobertura:1.0.7
   script:
     # convert report from jacoco to cobertura
     - 'python /opt/cover2cover.py build/jacoco/jacoco.xml src/main/java > build/cobertura.xml'