Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Add Linux ARM tests to CI #16

Merged
merged 4 commits into from
Jan 17, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion .github/workflows/ci.yaml
Original file line number Diff line number Diff line change
@@ -11,7 +11,7 @@ jobs:
strategy:
max-parallel: 4
matrix:
runs-on: [ubuntu-latest, ubuntu-24.04, ubuntu-22.04, ubuntu-20.04]
runs-on: [ubuntu-latest, ubuntu-24.04, ubuntu-22.04, ubuntu-20.04, ubuntu-24.04-arm, ubuntu-22.04-arm]
include:
- runs-on: ubuntu-latest
service-key: SERVICE_KEY
@@ -21,6 +21,10 @@ jobs:
service-key: SERVICE_KEY2
- runs-on: ubuntu-20.04
service-key: SERVICE_KEY3
- runs-on: ubuntu-24.04-arm
service-key: SERVICE_KEY_ARM1
- runs-on: ubuntu-22.04-arm
service-key: SERVICE_KEY_ARM2
runs-on: ${{ matrix.runs-on }}
steps:
- uses: actions/checkout@v4
@@ -48,6 +52,10 @@ jobs:
echo Calling $TEST_URL 🚀
curl -v $TEST_URL

- name: Print client logs
if: always()
run: journalctl -u twingate

- run: echo "SUCCESS!!! 🤩 This job's status is ${{ job.status }}."

test-windows:
15 changes: 14 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -27,4 +27,17 @@ To run action locally to debug you can use `act` (`brew install act`):
act -j test -s SERVICE_KEY --container-options "--cap-add NET_ADMIN --device /dev/net/tun"
```

It'll ask for `SERVICE_KEY` value interactively.
It'll ask for `SERVICE_KEY` value interactively.

# How To Release

When releasing a new tag (`v1.4` for example) we also have to update the latest major version (`v1` in this case)
to point to it.
Example steps:

```
git tag v1.4
git tag v1 -f
git push origin v1 v1.4 -f
gh release create v1.4 --generate-notes --verify-tag
```
Loading