diff options
| author | Steve Azzopardi <steveazz@outlook.com> | 2019-04-12 11:15:52 +0200 |
|---|---|---|
| committer | Steve Azzopardi <steveazz@outlook.com> | 2019-04-12 11:15:52 +0200 |
| commit | 4008c604d42c3fd3102d33d4f6d6786dd6fe6ee0 (patch) | |
| tree | f1793e9d52bd5bc214ac1d57d78e4de4e67ec915 | |
| parent | c47598bc1b7427429243db1e9dec0e26c2120df1 (diff) | |
| download | gitlab-ce-docs/add-cross-links.tar.gz | |
Add doc crosslink for GIT_CLEAN_FLAGSdocs/add-cross-links
| -rw-r--r-- | doc/ci/large_repositories/index.md | 29 |
1 files changed, 15 insertions, 14 deletions
diff --git a/doc/ci/large_repositories/index.md b/doc/ci/large_repositories/index.md index cf8ad88463f..244ccbb92b0 100644 --- a/doc/ci/large_repositories/index.md +++ b/doc/ci/large_repositories/index.md @@ -92,22 +92,23 @@ from disk. > Introduced in GitLab Runner 11.10. -`GIT_CLEAN_FLAGS` allows you to control whether or not you require -the `git clean` command to be executed for each CI job. -By default, GitLab ensures that you have your worktree on the given SHA, +[`GIT_CLEAN_FLAGS`](../yaml/README.md#git-clean-flags) allows you to control +whether or not you require the `git clean` command to be executed for each CI +job. By default, GitLab ensures that you have your worktree on the given SHA, and that your repository is clean. -`GIT_CLEAN_FLAGS` is disabled when set to `none`. On very big repositories, this -might be desired because `git clean` is disk I/O intensive. Controlling that -with `GIT_CLEAN_FLAGS: -ffdx -e .build/`, for example, allows you to control and -disable removal of some directories within the worktree between subsequent runs, -which can speed-up the incremental builds. This has the biggest effect -if you re-use existing machines, and have an existing worktree that you can re-use -for builds. - -For exact parameters accepted by `GIT_CLEAN_FLAGS`, see the documentation -for [git clean](https://git-scm.com/docs/git-clean). The -available parameters are dependent on Git version. +[`GIT_CLEAN_FLAGS`](../yaml/README.md#git-clean-flags) is disabled when set +to `none`. On very big repositories, this might be desired because `git +clean` is disk I/O intensive. Controlling that with `GIT_CLEAN_FLAGS: -ffdx +-e .build/`, for example, allows you to control and disable removal of some +directories within the worktree between subsequent runs, which can speed-up +the incremental builds. This has the biggest effect if you re-use existing +machines, and have an existing worktree that you can re-use for builds. + +For exact parameters accepted by +[`GIT_CLEAN_FLAGS`](../yaml/README.md#git-clean-flags), see the documentation +for [git clean](https://git-scm.com/docs/git-clean). The available parameters +are dependent on Git version. ## Fork-based workflow |