lavender-legacy
/
gitea
7
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Use vendors when go generate (#7340) 

* use vendors when go generate

* update docs about golang minimal requirement from 1.9 to 1.11

* fix build
release/v1.15
Lunny Xiao 2019-07-07 11:00:41 +08:00 committed by techknowlogick
parent f369788347
commit 87404d7c0b
4 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.drone.yml
View File

@ -63,9 +63,11 @@ steps:
- name: build-without-gcc - name: build-without-gcc
pull: always pull: always
image: golang:1.10 # this step is kept as the lowest version of golang that we support image: golang:1.11 # this step is kept as the lowest version of golang that we support
environment:
GO111MODULE: on
commands: commands:
- go build -o gitea_no_gcc # test if build succeeds without the sqlite tag - go build -mod=vendor -o gitea_no_gcc # test if build succeeds without the sqlite tag
- name: build - name: build
pull: always pull: always

2
Makefile
View File

@ -97,7 +97,7 @@ vet:
.PHONY: generate .PHONY: generate
generate: generate:
GO111MODULE=on $(GO) generate $(PACKAGES) GO111MODULE=on $(GO) generate -mod=vendor $(PACKAGES)
.PHONY: generate-swagger .PHONY: generate-swagger
generate-swagger: generate-swagger:

2
docs/content/doc/advanced/hacking-on-gitea.en-us.md
View File

@ -32,7 +32,7 @@ necessary. To be able to use these you must have the `"$GOPATH"/bin` directory
on the executable path. If you don't add the go bin directory to the on the executable path. If you don't add the go bin directory to the
executable path you will have to manage this yourself. executable path you will have to manage this yourself.
**Note 2**: Go version 1.9 or higher is required; however, it is important **Note 2**: Go version 1.11 or higher is required; however, it is important
to note that our continuous integration will check that the formatting of the to note that our continuous integration will check that the formatting of the
source code is not changed by `gofmt` using `make fmt-check`. Unfortunately, source code is not changed by `gofmt` using `make fmt-check`. Unfortunately,
the results of `gofmt` can differ by the version of `go`. It is therefore the results of `gofmt` can differ by the version of `go`. It is therefore

2
docs/content/doc/installation/from-source.en-us.md
View File

@ -27,7 +27,7 @@ necessary. To be able to use these, you must have the `"$GOPATH/bin"` directory
on the executable path. If you don't add the go bin directory to the on the executable path. If you don't add the go bin directory to the
executable path, you will have to manage this yourself. executable path, you will have to manage this yourself.
**Note 2**: Go version 1.9 or higher is required. However, it is recommended to **Note 2**: Go version 1.11 or higher is required. However, it is recommended to
obtain the same version as our continuous integration, see the advice given in obtain the same version as our continuous integration, see the advice given in
<a href='{{< relref "doc/advanced/hacking-on-gitea.en-us.md" >}}'>Hacking on <a href='{{< relref "doc/advanced/hacking-on-gitea.en-us.md" >}}'>Hacking on
Gitea</a> Gitea</a>