Mislav Marohnić
4e393fdab4
Avoid intermittent CI failures while setting up Go
...
Switch to `actions/setup-go@v2-beta` which advertises better retries
around downloading the Go version
2020-04-13 17:15:59 +02:00
Mislav Marohnić
876e825e64
Check code with golangci-lint on push
...
Right now linting failures don't fail the CI job, but they might in the
future.
2020-04-02 14:55:13 +02:00
Mislav Marohnić
ad190519c6
Simplify ANSI coloring
2020-04-01 15:09:24 +02:00
Mislav Marohnić
228312a30d
Have git diff produce colored output in CI
2020-04-01 14:48:47 +02:00
Mislav Marohnić
7dbc5e99e4
go: download dependencies before running tests in CI
2020-04-01 14:48:43 +02:00
Mislav Marohnić
a8894a0745
Assert that running go fmt or go mod tidy produces no changes in CI
...
This will help avoid introducing code changes that are not properly
formatted, or `go mod` dependency changes that are untidy.
Ref. 0680bb5c6c
2020-04-01 14:30:52 +02:00
Henrique Vicente
a1db5c3070
tests: adding the Go data race detector.
...
https://golang.org/doc/articles/race_detector.html
https://blog.golang.org/race-detector
2020-03-05 14:40:55 +01:00
Mislav Marohnić
5f6fd35a99
Enable CI for pull requests from forks
2020-02-17 12:52:48 +01:00
Mislav Marohnić
8aa46ab0f2
Merge pull request #276 from cli/rework-release
...
Add more binary builds, simplify release process
2020-01-30 19:33:21 +01:00
Mislav Marohnić
10d46fe869
Consistently use checkout@v2
2020-01-29 15:28:06 +01:00
Mislav Marohnić
4e579e544c
Make sure failed builds result in an error on Windows
...
By default, this was run on PowerShell on Windows, and even though the
Actions environment is supposed to immediately exit on failures[1], this
doesn't seem to have effect.
Switching to bash for unified behavior on all platforms.
[1]: https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#exit-codes-and-error-action-preference
2020-01-29 12:22:13 +01:00
Mislav Marohnić
eb6541d8d6
Fix CI build
2020-01-23 11:03:06 +01:00
Mislav Marohnić
a3c808e22e
Disable cancelling other CI builds after one fails
...
https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast
2020-01-15 12:56:00 +01:00
Mislav Marohnić
0639ef8445
Cleanup unnecessary workflow bits
2020-01-08 17:17:40 +01:00
Mislav Marohnić
82b0986a6c
Use build matrix for CI job
...
https://help.github.com/en/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix
2020-01-06 20:42:18 +01:00
Nate Smith
2e192d7284
be more descriptive
2019-12-23 22:00:58 -06:00
vilmibm
5c05b60ab2
give unique names
2019-12-20 10:29:12 -06:00
vilmibm
2ba17b4126
build on all three supported OSs
2019-12-20 10:24:34 -06:00
Corey Johnson
4e61c3ea73
Fix syntax
2019-12-17 16:19:30 -08:00
Mislav Marohnić
6d8af20e30
Stop requiring vendored dependencies in CI
...
We started vendoring dependencies because this was a practice that the Go community had for a while now to:
1. Speed up builds - no need to fetch dependencies every time;
2. Guard against 3rd-party downtime - CI passes even if hosts such as `gopkg.in` are down, or if someone deletes their GitHub repo/account hosting a particular module.
With Go 1.13 and GitHub Actions, however, we have these problems solved for free:
- The built-in goproxy caches dependencies and speeds up downloads;
- Octofactory ensures that dependencies are cached on our own infrastructure, guarding us from 3rd-party downtime.
With all this in mind, I feel that we don't have to require vendoring dependencies anymore.
2019-10-23 22:35:11 +02:00
Mislav Marohnić
334b1ae9fe
Add CI
2019-10-04 09:10:17 +02:00
