ooni-probe-cli/.github/workflows/qatelegram.yml

# qatelegram runs QA checks for the telegram experiment
name: "qatelegram"
on:
  push:
    branches:
      - "release/**"
jobs:
  test:
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/setup-go@v1
        with:
          go-version: "1.17.6"
      - uses: actions/checkout@v2
      - run: ./QA/rundocker.bash "telegram"
refactor(.github/workflows): reorganize many builds (#332) 1. reduce the number of periodic builds 2. just build as part of the release process in most cases 3. shorttests duplicates coverage Preliminary changes as part of https://github.com/ooni/probe/issues/1466 2021-05-06 19:56:55 +02:00			`# qatelegram runs QA checks for the telegram experiment`
chore: merge probe-engine into probe-cli (#201) This is how I did it: 1. `git clone https://github.com/ooni/probe-engine internal/engine` 2. ``` (cd internal/engine && git describe --tags) v0.23.0 ``` 3. `nvim go.mod` (merging `go.mod` with `internal/engine/go.mod` 4. `rm -rf internal/.git internal/engine/go.{mod,sum}` 5. `git add internal/engine` 6. `find . -type f -name \*.go -exec sed -i 's@/ooni/probe-engine@/ooni/probe-cli/v3/internal/engine@g' {} \;` 7. `go build ./...` (passes) 8. `go test -race ./...` (temporary failure on RiseupVPN) 9. `go mod tidy` 10. this commit message Once this piece of work is done, we can build a new version of `ooniprobe` that is using `internal/engine` directly. We need to do more work to ensure all the other functionality in `probe-engine` (e.g. making mobile packages) are still WAI. Part of https://github.com/ooni/probe/issues/1335 2021-02-02 12:05:47 +01:00			`name: "qatelegram"`
			`on:`
refactor: enable QA tests and jafar self test (#208) * refactor: enable QA tests and jafar self test Part of https://github.com/ooni/probe/issues/1335 * chore: make sure all workflows run on release branches 2021-02-03 13:20:37 +01:00			`push:`
			`branches:`
refactor(.github/workflows): reorganize many builds (#332) 1. reduce the number of periodic builds 2. just build as part of the release process in most cases 3. shorttests duplicates coverage Preliminary changes as part of https://github.com/ooni/probe/issues/1466 2021-05-06 19:56:55 +02:00			`- "release/**"`
chore: merge probe-engine into probe-cli (#201) This is how I did it: 1. `git clone https://github.com/ooni/probe-engine internal/engine` 2. ``` (cd internal/engine && git describe --tags) v0.23.0 ``` 3. `nvim go.mod` (merging `go.mod` with `internal/engine/go.mod` 4. `rm -rf internal/.git internal/engine/go.{mod,sum}` 5. `git add internal/engine` 6. `find . -type f -name \*.go -exec sed -i 's@/ooni/probe-engine@/ooni/probe-cli/v3/internal/engine@g' {} \;` 7. `go build ./...` (passes) 8. `go test -race ./...` (temporary failure on RiseupVPN) 9. `go mod tidy` 10. this commit message Once this piece of work is done, we can build a new version of `ooniprobe` that is using `internal/engine` directly. We need to do more work to ensure all the other functionality in `probe-engine` (e.g. making mobile packages) are still WAI. Part of https://github.com/ooni/probe/issues/1335 2021-02-02 12:05:47 +01:00			`jobs:`
			`test:`
refactor(.github/workflows): reorganize many builds (#332) 1. reduce the number of periodic builds 2. just build as part of the release process in most cases 3. shorttests duplicates coverage Preliminary changes as part of https://github.com/ooni/probe/issues/1466 2021-05-06 19:56:55 +02:00			`runs-on: ubuntu-20.04`
chore: merge probe-engine into probe-cli (#201) This is how I did it: 1. `git clone https://github.com/ooni/probe-engine internal/engine` 2. ``` (cd internal/engine && git describe --tags) v0.23.0 ``` 3. `nvim go.mod` (merging `go.mod` with `internal/engine/go.mod` 4. `rm -rf internal/.git internal/engine/go.{mod,sum}` 5. `git add internal/engine` 6. `find . -type f -name \*.go -exec sed -i 's@/ooni/probe-engine@/ooni/probe-cli/v3/internal/engine@g' {} \;` 7. `go build ./...` (passes) 8. `go test -race ./...` (temporary failure on RiseupVPN) 9. `go mod tidy` 10. this commit message Once this piece of work is done, we can build a new version of `ooniprobe` that is using `internal/engine` directly. We need to do more work to ensure all the other functionality in `probe-engine` (e.g. making mobile packages) are still WAI. Part of https://github.com/ooni/probe/issues/1335 2021-02-02 12:05:47 +01:00			`steps:`
			`- uses: actions/setup-go@v1`
			`with:`
chore: use go1.17.6 (#664) We're starting to prepare a new release. The first step is to use go1.17.6 in the following places: 1. everywhere we define the version of Go in this tree; 2. when we're building for Android (using ooni/go); 3. in our ooni/oohttp fork of Go net/http standard library. Reference issue: https://github.com/ooni/probe/issues/1845 2022-01-18 12:50:24 +01:00			`go-version: "1.17.6"`
chore: merge probe-engine into probe-cli (#201) This is how I did it: 1. `git clone https://github.com/ooni/probe-engine internal/engine` 2. ``` (cd internal/engine && git describe --tags) v0.23.0 ``` 3. `nvim go.mod` (merging `go.mod` with `internal/engine/go.mod` 4. `rm -rf internal/.git internal/engine/go.{mod,sum}` 5. `git add internal/engine` 6. `find . -type f -name \*.go -exec sed -i 's@/ooni/probe-engine@/ooni/probe-cli/v3/internal/engine@g' {} \;` 7. `go build ./...` (passes) 8. `go test -race ./...` (temporary failure on RiseupVPN) 9. `go mod tidy` 10. this commit message Once this piece of work is done, we can build a new version of `ooniprobe` that is using `internal/engine` directly. We need to do more work to ensure all the other functionality in `probe-engine` (e.g. making mobile packages) are still WAI. Part of https://github.com/ooni/probe/issues/1335 2021-02-02 12:05:47 +01:00			`- uses: actions/checkout@v2`
			`- run: ./QA/rundocker.bash "telegram"`