feat: implement rolling builds (#910)
This diff modifies all the github actions that produce assets to publish on a release called rolling when we are not building a tag. If everything goes as planned, we should be able to provide people with automatically generated fresh binaries for testing. While there, introduce caching for all builds to make them as fast as possible. I suspect gomobile based builds will not see any speed up but other builds most likely will. See https://github.com/ooni/probe/issues/2249
This commit is contained in:
parent
d1b172f3ac
commit
d10ab88444
19 changed files with 111 additions and 151 deletions
3
.github/workflows/alltests.yml
vendored
3
.github/workflows/alltests.yml
vendored
|
|
@ -16,8 +16,9 @@ jobs:
|
|||
id: goversion
|
||||
run: echo ::set-output name=version::$(cat GOVERSION)
|
||||
|
||||
- uses: actions/setup-go@v3
|
||||
- uses: magnetikonline/action-golang-cache@v2
|
||||
with:
|
||||
go-version: "${{ steps.goversion.outputs.version }}"
|
||||
cache-key-suffix: "-alltests-${{ steps.goversion.outputs.version }}"
|
||||
|
||||
- run: go test -race -tags shaping ./...
|
||||
|
|
|
|||
Loading…
Reference in a new issue