letsencrypt / ct-woodpecker / 959

69%

main: 68%

cron

travis-ci

<a href="https://github.com/letsencrypt/ct-woodpecker/commit/<a class=hub.com/letsencrypt/ct-woodpecker/commit/1af59592cce56ba09bc68d8357e0fe33f7903306">1af59592c<a href="https://github.com/letsencrypt/ct-woodpecker/commit/1af59592cce56ba09bc68d8357e0fe33f7903306">&quot;&gt;CI: switch to Go 1.13, update golangci-lint, avoid module download. (#107)

One of the transitive dependencies of `ct-woodpecker` seems to have
moved/gone away causing consistent build failures of the form:
```
go: git.apache.org/thrift.git@v0.0.0-20180902110319-2566ecd5d999: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/travis/gopath/pkg/mod/cache/vcs/</a><a class="double-link" href="https://github.com/letsencrypt/ct-woodpecker/commit/<a class="double-link" href="https://github.com/letsencrypt/ct-woodpecker/commit/83dba939f95a790e497d565fc4418400145a1a51">83dba939f</a>">83dba939f</a><a href="https://github.com/letsencrypt/ct-woodpecker/commit/1af59592cce56ba09bc68d8357e0fe33f7903306">4f955fa052f662d56e920c3e: exit status 128:
	fatal: unable to access &#39;https://git.apache.org/thrift.git/&#39;: Failed to connect to git.apache.org port 443: Connection timed out
```

We already vendor dependencies to avoid this sort of problem. The
easiest &quot;fix&quot; in this case was to remove a workaround `go mod download`
we did to appease earlier `golangci-lint` versions.

In short:
* Updated to Go 1.13 (why not)
* Updated `golangci-lint`
* Removed `go mod download`.
* Removed unneeded `GO111MODULE=on` env var

860 of 1242 relevant lines covered (69.24%)

4.69 hits per line