summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-04-10 03:09:25 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-04-10 03:09:25 +0000
commita7dc052b7e01aee680d130274c79da9bfa459272 (patch)
treee38452234d8eea36865f169377bb736912d481fe
parent1bf4fece121298260663c6ca73d39716d3548a03 (diff)
downloadgitlab-ce-a7dc052b7e01aee680d130274c79da9bfa459272.tar.gz
Add latest changes from gitlab-org/gitlab@master
-rw-r--r--doc/development/go_guide/index.md19
1 files changed, 2 insertions, 17 deletions
diff --git a/doc/development/go_guide/index.md b/doc/development/go_guide/index.md
index d23c10f19d4..975b524c1df 100644
--- a/doc/development/go_guide/index.md
+++ b/doc/development/go_guide/index.md
@@ -130,23 +130,8 @@ projects, and makes merge requests easier to review.
In some cases, such as building a Go project for it to act as a dependency of a
CI run for another project, removing the `vendor/` directory means the code must
be downloaded repeatedly, which can lead to intermittent problems due to rate
-limiting or network failures. In these circumstances, you should cache the
-downloaded code between runs with a `.gitlab-ci.yml` snippet like this:
-
-```yaml
-.go-cache:
- variables:
- GOPATH: $CI_PROJECT_DIR/.go
- before_script:
- - mkdir -p .go
- cache:
- paths:
- - .go/pkg/mod/
-
-test:
- extends: .go-cache
- # ...
-```
+limiting or network failures. In these circumstances, you should [cache the
+downloaded code between](../../ci/caching/index.md#caching-go-dependencies).
There was a [bug on modules
checksums](https://github.com/golang/go/issues/29278) in Go < v1.11.4, so make