d10ab88444
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
27 lines
621 B
YAML
27 lines
621 B
YAML
# Checks whether the jafar tool is still WAI.
|
|
name: jafar
|
|
on:
|
|
push:
|
|
branches:
|
|
- "release/**"
|
|
- "fullbuild"
|
|
|
|
jobs:
|
|
test:
|
|
runs-on: ubuntu-20.04
|
|
steps:
|
|
- uses: actions/checkout@v2
|
|
|
|
- name: Get GOVERSION content
|
|
id: goversion
|
|
run: echo ::set-output name=version::$(cat GOVERSION)
|
|
|
|
- uses: magnetikonline/action-golang-cache@v2
|
|
with:
|
|
go-version: "${{ steps.goversion.outputs.version }}"
|
|
cache-key-suffix: "-jafar-${{ steps.goversion.outputs.version }}"
|
|
|
|
- run: go build -v ./internal/cmd/jafar
|
|
|
|
- run: sudo ./testjafar.bash
|