pool/tools/Dockerfile

FROM golang:1.19.4

RUN apt-get update && apt-get install -y git
ENV GOCACHE=/tmp/build/.cache
ENV GOMODCACHE=/tmp/build/.modcache
ENV GOFLAGS="-buildvcs=false"

COPY . /tmp/tools

RUN cd /tmp \
  && mkdir -p /tmp/build/.cache \
  && mkdir -p /tmp/build/.modcache \
  && cd /tmp/tools \
  && go install -trimpath github.com/golangci/golangci-lint/cmd/golangci-lint \
  && chmod -R 777 /tmp/build/

WORKDIR /build
build: update go to v1.19.4-beta 2023-01-04 13:58:08 -08:00			`FROM golang:1.19.4`
tools+make+lint: use dockerized tools 2022-08-03 19:51:06 +02:00
			`RUN apt-get update && apt-get install -y git`
			`ENV GOCACHE=/tmp/build/.cache`
			`ENV GOMODCACHE=/tmp/build/.modcache`
tools: fix linter issue with go 1.19 2023-02-08 17:05:34 +01:00			`ENV GOFLAGS="-buildvcs=false"`
tools+make+lint: use dockerized tools 2022-08-03 19:51:06 +02:00
			`COPY . /tmp/tools`

			`RUN cd /tmp \`
			`&& mkdir -p /tmp/build/.cache \`
			`&& mkdir -p /tmp/build/.modcache \`
			`&& cd /tmp/tools \`
make+tools: don't compile with build tag to avoid collision It looks like one of the projects pulled in by the linter also uses the "tools" build tag. When we turn on that build tag, we get build errors in github.com/ryancurrah/gomodguard. So we just remove the build tag during compilation as it's not actually needed (the build tag is just there to not pull in the dependencies during the normal build). 2023-02-23 11:09:35 +01:00			`&& go install -trimpath github.com/golangci/golangci-lint/cmd/golangci-lint \`
Revert "ci: fix lint VSC permissions error" This reverts commit ad3d2d943bf2680419b4109b578bb884eb7ca4b9. 2023-01-06 08:31:40 -08:00			`&& chmod -R 777 /tmp/build/`
tools+make+lint: use dockerized tools 2022-08-03 19:51:06 +02:00
build: update go to v1.19.4-beta 2023-01-04 13:58:08 -08:00			`WORKDIR /build`