c/ooni-probe-cli
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
b2209bb637
ooni-probe-cli/.github/workflows/linux.yml

54 lines
2.1 KiB
YAML
Raw Normal View History

refactor(.github/workflows): linux: use ./make, run less frequently (#334) While there, flush `print`s in `./make` to have more understandable logging. Also part of https://github.com/ooni/probe/issues/1466
2021-05-06 20:44:56 +02:00
# linux builds ooniprobe for Linux
WIP: Start preparing release v3.0.7 (#147) * Use ooni/probe-engine 0.16.0 * Update all the other dependencies * Use GitHub Actions rather than Travis CI * Automatically build and test binaries on the target OS (for Windows, macOS, Linux on amd64) * Make sure we correctly measure coverage * Make sure we use `-race` when running tests * Remove unnecessary scripts * Make sure the README is up-to-date * Write small script to update binary data and add GitHub Actions checks for it * Notice that we needed to run ./updatebindata.sh and run it * Self documenting instructions regarding cross compiling * Set version number to v3.0.7-beta Part of https://github.com/ooni/probe-engine/issues/748
2020-08-22 11:20:50 +02:00
name: linux
on:
push:
refactor(.github/workflows): linux: use ./make, run less frequently (#334) While there, flush `print`s in `./make` to have more understandable logging. Also part of https://github.com/ooni/probe/issues/1466
2021-05-06 20:44:56 +02:00
branches:
- "release/**"
feat(gha/linux): upload deb packages for arm64 (#337) We're still working on https://github.com/ooni/probe/issues/1466. The idea here is to teach the GH action for Linux to publish the debian package for arm64. When this is done, we can cleanup legacy build scripts and GH actions, because there is no remaining use case for them: we now build everything using the `./make` tool.
2021-05-07 09:22:46 +02:00
jobs:
refactor(.github/workflows): linux: use ./make, run less frequently (#334) While there, flush `print`s in `./make` to have more understandable logging. Also part of https://github.com/ooni/probe/issues/1466
2021-05-06 20:44:56 +02:00
build_amd64:
runs-on: "ubuntu-20.04"
WIP: Start preparing release v3.0.7 (#147) * Use ooni/probe-engine 0.16.0 * Update all the other dependencies * Use GitHub Actions rather than Travis CI * Automatically build and test binaries on the target OS (for Windows, macOS, Linux on amd64) * Make sure we correctly measure coverage * Make sure we use `-race` when running tests * Remove unnecessary scripts * Make sure the README is up-to-date * Write small script to update binary data and add GitHub Actions checks for it * Notice that we needed to run ./updatebindata.sh and run it * Self documenting instructions regarding cross compiling * Set version number to v3.0.7-beta Part of https://github.com/ooni/probe-engine/issues/748
2020-08-22 11:20:50 +02:00
steps:
refactor(.github/workflows): linux: use ./make, run less frequently (#334) While there, flush `print`s in `./make` to have more understandable logging. Also part of https://github.com/ooni/probe/issues/1466
2021-05-06 20:44:56 +02:00
- run: |
build.sh: build windows/386 and linux/386, update Debian packaging (#193) * feat(build.sh): build for windows/386 Part of https://github.com/ooni/probe/issues/1315 * fix(build.sh): docker pull so we have latest image Part of https://github.com/ooni/probe/issues/1315 * fix(build.sh): apk update && apk upgrade to have latest packages It does not currently seem necessary. But let's be defensive. Part of https://github.com/ooni/probe/issues/1315. * fix(windows.yml): for now disable windows/386 It's working locally but not remotely on Windows. We need to figure out how to install the 386 compiler. Part of https://github.com/ooni/probe/issues/1315. * feat(build.sh): build for windows/386 Part of https://github.com/ooni/probe/issues/1315. * fix(linux.yml): try to enable experimental docker flags Related to https://github.com/ooni/probe/issues/1315. See also https://github.com/actions/virtual-environments/issues/368#issuecomment-713588127. * fix(debian): try to have single workflow with experimental docker More commits probably needed. Part of https://github.com/ooni/ooni.org/issues/677. * remove restriction on the branch name * maybe we need a pattern also for branches * less stringent constraints * consolidated debian workflow into a single workflow * further fix the debian workflow * only run debian action for specific branches or tags * fix(build.sh): package the 386 windows version properly
2021-01-20 13:09:37 +01:00
echo $'{\n "experimental": true\n}' | sudo tee /etc/docker/daemon.json
sudo service docker restart
WIP: Start preparing release v3.0.7 (#147) * Use ooni/probe-engine 0.16.0 * Update all the other dependencies * Use GitHub Actions rather than Travis CI * Automatically build and test binaries on the target OS (for Windows, macOS, Linux on amd64) * Make sure we correctly measure coverage * Make sure we use `-race` when running tests * Remove unnecessary scripts * Make sure the README is up-to-date * Write small script to update binary data and add GitHub Actions checks for it * Notice that we needed to run ./updatebindata.sh and run it * Self documenting instructions regarding cross compiling * Set version number to v3.0.7-beta Part of https://github.com/ooni/probe-engine/issues/748
2020-08-22 11:20:50 +02:00
- uses: actions/checkout@v2
refactor: replace ./make (python3) with ./mk (makefile) (#343) This pull request fixes https://github.com/ooni/probe/issues/1471. We have replaced the original build script (`./make`) with the `./mk` makefile (executable using `#!/usr/bin/make -f`). We concluded supporting direct builds from Windows is not worth the effort and halving the code we need to maintain is probably a good plus. Both macOS and Linux install GNU make at `/usr/bin/make`, so we should be okay in the common use cases. I significantly simplified the management of Go versioning by requiring the user to manage it and by enforcing that we are using the desired Go version. This speeds up builds and works in sane operating systems that use the last version of a specific package. Otherwise, it's possible to use the `go get golang.org/dl/go${version}` feature. The remaining question mark was related to updating the Android SDK. I have determined that a good course of action is pinning to the latest CLI tools and always forcing the CLI tools to install the latest required packages (e.g., the NDK).
2021-05-11 16:15:13 +02:00
- run: ./mk OONI_PSIPHON_TAGS="" ./CLI/linux/amd64/ooniprobe
refactor(.github/workflows): linux: use ./make, run less frequently (#334) While there, flush `print`s in `./make` to have more understandable logging. Also part of https://github.com/ooni/probe/issues/1466
2021-05-06 20:44:56 +02:00
env:
DOCKER_CLI_EXPERIMENTAL: enabled
WIP: Start preparing release v3.0.7 (#147) * Use ooni/probe-engine 0.16.0 * Update all the other dependencies * Use GitHub Actions rather than Travis CI * Automatically build and test binaries on the target OS (for Windows, macOS, Linux on amd64) * Make sure we correctly measure coverage * Make sure we use `-race` when running tests * Remove unnecessary scripts * Make sure the README is up-to-date * Write small script to update binary data and add GitHub Actions checks for it * Notice that we needed to run ./updatebindata.sh and run it * Self documenting instructions regarding cross compiling * Set version number to v3.0.7-beta Part of https://github.com/ooni/probe-engine/issues/748
2020-08-22 11:20:50 +02:00
- run: ./smoketest.sh ./CLI/linux/amd64/ooniprobe
refactor: replace ./make (python3) with ./mk (makefile) (#343) This pull request fixes https://github.com/ooni/probe/issues/1471. We have replaced the original build script (`./make`) with the `./mk` makefile (executable using `#!/usr/bin/make -f`). We concluded supporting direct builds from Windows is not worth the effort and halving the code we need to maintain is probably a good plus. Both macOS and Linux install GNU make at `/usr/bin/make`, so we should be okay in the common use cases. I significantly simplified the management of Go versioning by requiring the user to manage it and by enforcing that we are using the desired Go version. This speeds up builds and works in sane operating systems that use the last version of a specific package. Otherwise, it's possible to use the `go get golang.org/dl/go${version}` feature. The remaining question mark was related to updating the Android SDK. I have determined that a good course of action is pinning to the latest CLI tools and always forcing the CLI tools to install the latest required packages (e.g., the NDK).
2021-05-11 16:15:13 +02:00
- run: ./mk OONI_PSIPHON_TAGS="" DEBIAN_TILDE_VERSION=$GITHUB_RUN_NUMBER ./debian/amd64
feat(gha/linux): upload deb packages for arm64 (#337) We're still working on https://github.com/ooni/probe/issues/1466. The idea here is to teach the GH action for Linux to publish the debian package for arm64. When this is done, we can cleanup legacy build scripts and GH actions, because there is no remaining use case for them: we now build everything using the `./make` tool.
2021-05-07 09:22:46 +02:00
- run: sudo apt-get install -y --no-install-recommends git python3 python3-requests python3-gnupg s3cmd
- run: |
for deb in *.deb; do
./.github/workflows/debops-ci --arch amd64 --show-commands upload --bucket-name ooni-deb $deb
done
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
DEB_GPG_KEY: ${{ secrets.DEB_GPG_KEY }}
refactor(.github/workflows): linux: use ./make, run less frequently (#334) While there, flush `print`s in `./make` to have more understandable logging. Also part of https://github.com/ooni/probe/issues/1466
2021-05-06 20:44:56 +02:00
build_arm64:
runs-on: "ubuntu-20.04"
steps:
- run: |
echo $'{\n "experimental": true\n}' | sudo tee /etc/docker/daemon.json
sudo service docker restart
- uses: actions/checkout@v2
refactor: replace ./make (python3) with ./mk (makefile) (#343) This pull request fixes https://github.com/ooni/probe/issues/1471. We have replaced the original build script (`./make`) with the `./mk` makefile (executable using `#!/usr/bin/make -f`). We concluded supporting direct builds from Windows is not worth the effort and halving the code we need to maintain is probably a good plus. Both macOS and Linux install GNU make at `/usr/bin/make`, so we should be okay in the common use cases. I significantly simplified the management of Go versioning by requiring the user to manage it and by enforcing that we are using the desired Go version. This speeds up builds and works in sane operating systems that use the last version of a specific package. Otherwise, it's possible to use the `go get golang.org/dl/go${version}` feature. The remaining question mark was related to updating the Android SDK. I have determined that a good course of action is pinning to the latest CLI tools and always forcing the CLI tools to install the latest required packages (e.g., the NDK).
2021-05-11 16:15:13 +02:00
- run: sudo apt-get update -q
- run: sudo apt-get install -y qemu-user-static
- run: ./mk OONI_PSIPHON_TAGS="" ./CLI/linux/arm64/ooniprobe
refactor(.github/workflows): linux: use ./make, run less frequently (#334) While there, flush `print`s in `./make` to have more understandable logging. Also part of https://github.com/ooni/probe/issues/1466
2021-05-06 20:44:56 +02:00
env:
DOCKER_CLI_EXPERIMENTAL: enabled
- run: ./smoketest.sh ./CLI/linux/arm64/ooniprobe
refactor: replace ./make (python3) with ./mk (makefile) (#343) This pull request fixes https://github.com/ooni/probe/issues/1471. We have replaced the original build script (`./make`) with the `./mk` makefile (executable using `#!/usr/bin/make -f`). We concluded supporting direct builds from Windows is not worth the effort and halving the code we need to maintain is probably a good plus. Both macOS and Linux install GNU make at `/usr/bin/make`, so we should be okay in the common use cases. I significantly simplified the management of Go versioning by requiring the user to manage it and by enforcing that we are using the desired Go version. This speeds up builds and works in sane operating systems that use the last version of a specific package. Otherwise, it's possible to use the `go get golang.org/dl/go${version}` feature. The remaining question mark was related to updating the Android SDK. I have determined that a good course of action is pinning to the latest CLI tools and always forcing the CLI tools to install the latest required packages (e.g., the NDK).
2021-05-11 16:15:13 +02:00
- run: ./mk OONI_PSIPHON_TAGS="" DEBIAN_TILDE_VERSION=$GITHUB_RUN_NUMBER ./debian/arm64
feat(gha/linux): upload deb packages for arm64 (#337) We're still working on https://github.com/ooni/probe/issues/1466. The idea here is to teach the GH action for Linux to publish the debian package for arm64. When this is done, we can cleanup legacy build scripts and GH actions, because there is no remaining use case for them: we now build everything using the `./make` tool.
2021-05-07 09:22:46 +02:00
- run: sudo apt-get install -y --no-install-recommends git python3 python3-requests python3-gnupg s3cmd
- run: |
for deb in *.deb; do
./.github/workflows/debops-ci --arch arm64 --show-commands upload --bucket-name ooni-deb $deb
done
env:
AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
DEB_GPG_KEY: ${{ secrets.DEB_GPG_KEY }}
Reference in New Issue Copy Permalink