Go to file
Simone Basso fdbf871103
[forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611)
This diff forwardports 856e436e20d511a4f0d618546da7921fa9f8c5f6 to the master branch

Original commit message:

- - -

This pull request changes `mk` and github workflows to build and publish binaries on tag. We also update the documentation to explain this new branching model. Basically, we have release branches where we produce binary packages and we add extra code, on tag, to publish such packages inside a release.

We discussed removing most secrets from builds in this repository and having a different tool/repository that takes in input also secrets for doing follow-up actions after publishing. As a consequence, this pull request also removes all pieces of code that require secrets. The next step is to reinstate this code in this new repository/tool.

The existing code in `mk` also implemented caching. This feature was useful when doing local builds because it reduced the time required to obtain binary releases. With builds running as part of GitHub actions, we don't need caching because we spawn parallel machines to build binaries. Therefore, let us also remove caching, which makes the code simpler. (Caching in itself is hard and in https://github.com/ooni/probe/issues/1875 I noted that, for example, caching of the `ooni/go` repository was leading to some unwanted behaviour when changing the branch. Without caching, this behaviour is gone and we always generally use fresh information to produce builds.) Of course, this means that local builds are now slower, but I do not think this is a problem _because_ we want to use GitHub actions for building in the common case.

Reference issues: https://github.com/ooni/probe/issues/1879 and https://github.com/ooni/probe/issues/1875.

The final aspect to mention to conclude this description is an implementation one:

```
          gh release create -p $tag --target $GITHUB_SHA || true
```

The code above uses `|| true` because there could already be a release. So, basically, it means that, if a release does not already exist, then we're going to create one. Otherwise, it does not matter because there's already a release.
2021-11-23 15:56:25 +01:00
.github/workflows [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
.vscode feat(make): sign more generated binaries (#330) 2021-05-05 14:26:19 +02:00
CLI [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
cmd cleanup(ooniprobe): remove unused send_crash_report option (#578) 2021-11-05 13:26:08 +01:00
docs [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
E2E fix(ci/debianrepo): avoid running docker arm64 (#551) 2021-10-21 16:55:00 +02:00
internal [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
MOBILE [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
pkg feat(engine): allow runner to return many measurements (#527) 2021-09-30 00:54:52 +02:00
QA feat(QA): add test cases for websteps vs webconnectivity (#583) 2021-11-05 15:56:04 +01:00
testdata feat: introduce ptx package for pluggable transports dialers (#373) 2021-06-14 10:20:54 +02:00
.eslintrc.json feat(QA): add test cases for websteps vs webconnectivity (#583) 2021-11-05 15:56:04 +01:00
.gitignore feat(QA): add test cases for websteps vs webconnectivity (#583) 2021-11-05 15:56:04 +01:00
CODE_OF_CONDUCT.md doc: add code of conduct (#157) 2020-11-03 21:16:04 +01:00
CODEOWNERS chore: continue merging probe-engine into probe-cli (#211) 2021-02-03 14:42:51 +01:00
CONTRIBUTING.md [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
go.mod [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
go.sum [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
LICENSE feat: relicense the repository under GNU GPLv3 (#446) 2021-08-20 14:50:46 +02:00
mk [forwardport] ci/cd: publish binaries onto a release when we create a tag (#609) (#611) 2021-11-23 15:56:25 +01:00
PULL_REQUEST_TEMPLATE.md fix: improve the pull request template (#439) 2021-08-18 11:46:37 +02:00
Readme.md doc(readme): improve the content and organisation (#557) 2021-10-22 17:02:18 +02:00
testjafar.bash refactor: enable QA tests and jafar self test (#208) 2021-02-03 13:20:37 +01:00

OONI Probe Client Library and CLI

GoDoc Short Tests Status Coverage Status Go Report Card linux-debian-packages

The Open Observatory of Network Interference (OONI) is a non-profit free software project that aims to empower decentralized efforts in documenting Internet censorship around the world.

This repository contains core OONI tools written in Go:

Every top-level directory in this repository contains an explanatory README file.

User setup

Please, follow the instructions at ooni.org/install/cli to install ooniprobe. If we do not support your use case, please let us know. Once ooniprobe is installed, try ooniprobe help to get interactive help.

Reporting issues

Report issues at github.com/ooni/probe. Please, make sure you add the ooni/probe-cli label.

Build instructions

ooniprobe

Be sure you have golang >= 1.17 and a C compiler (Mingw-w64 for Windows). You can build using:

go build -v ./cmd/ooniprobe

This will generate a binary called ooniprobe in the current directory.

Android bindings

Make sure you have GNU make installed, then run:

./mk android

to build bindings for Android. (Add OONI_PSIPHON_TAGS="" if you cannot clone private repositories in the https://github.com/ooni namespace.)

The generated bindings are (manually) pushed to the Maven Central package repository. The instructions explaining how to integrate these bindings are published along with the release notes.

iOS bindings

Make sure you have GNU make installed, then run:

./mk ios

to build bindings for iOS. (Add OONI_PSIPHON_TAGS="" if you cannot clone private repositories in the https://github.com/ooni namespace.)

The generated bindings are (manually) added to GitHub releases. The instructions explaining how to integrate these bindings are published along with the release notes.

miniooni

Miniooni is the experimental OONI client used for research. Compile using:

go build -v ./internal/cmd/miniooni

This will generate a binary called miniooni in the current directory.

oohelperd

Oohelperd is the test helper server. Compile using:

go build -v ./internal/cmd/oohelperd

This will generate a binary called oohelperd in the current directory.

Specifications

Every nettest (aka experiment) implemented in this repository has a companion spec in the ooni/spec repository.

Contributing

Please, see CONTRIBUTING.md.

Updating dependencies

go get -u -v ./... && go mod tidy

Releasing

Create an issue according to the routine release template and perform any item inside the check-list.

We build releases using ./mk, which requires GNU make. Try the ./mk help|less command for detailed usage.