Source .env from beacon7 instead of Gitea secrets

TX_URL and TX_PASSWORD are read from ~/testsuite_tx_ui/.env on the runner host rather than Gitea repo secrets, which aren't configured. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Add Gitea Actions hardware CI pipeline
2026-06-19 15:55:55 +02:00 · 2026-06-19 15:48:10 +02:00 · 2026-04-30 17:12:25 +02:00 · 2026-04-30 17:07:28 +02:00 · 2026-04-30 13:47:40 +02:00
1 changed files with 38 additions and 0 deletions
@@ -0,0 +1,38 @@
 name: Hardware CI
 on:
  push:
    branches:
      - '**'
 # Only one run at a time — we have a single physical DUT.
 # A new push will queue behind the running job rather than cancelling it.
 concurrency:
  group: hw-dut
  cancel-in-progress: false
 jobs:
  hw-test:
    name: DUT update + UI tests
    runs-on: self-hosted
    timeout-minutes: 30
    steps:
      - name: Update DUT firmware
        run: |
          BRANCH="${{ github.ref_name }}"
          ssh -o StrictHostKeyChecking=no caster@swtx1008.local "
            set -e
            cd ~/bumble-auracast
            git fetch origin
            git checkout \"$BRANCH\" 2>/dev/null || git checkout -b \"$BRANCH\" origin/\"$BRANCH\"
            git pull origin \"$BRANCH\"
            bash src/auracast/server/system_update.sh
          "
      - name: Run UI regression tests
        run: |
          cd ~/testsuite_tx_ui
          git pull
          set -a && source .env && set +a
          ~/.local/bin/poetry run pytest -v
Author	SHA1	Message	Date
pstruebi	f4b35e3385	Source .env from beacon7 instead of Gitea secrets Hardware CI / DUT update + UI tests (push) Failing after 21m19s Details TX_URL and TX_PASSWORD are read from ~/testsuite_tx_ui/.env on the runner host rather than Gitea repo secrets, which aren't configured. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-19 15:55:55 +02:00
pstruebi	57386a0fc1	Add Gitea Actions hardware CI pipeline Hardware CI / DUT update + UI tests (push) Waiting to run Details Triggers on every push to every branch. Serialised via a concurrency group (cancel-in-progress: false) so only one run executes at a time against the single physical DUT. Pipeline steps (run on beacon7 self-hosted runner): 1. SSH into swtx1008, checkout the triggering branch, run system_update.sh (flashes nRF54L dongles, restarts services) 2. Run Playwright/pytest UI regression suite from ~/testsuite_tx_ui TX_URL and TX_PASSWORD are injected as Gitea repo secrets. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>	2026-06-19 15:48:10 +02:00
pstruebi	4f7e2bf888	Clarify advertising TX power handling and work around Bumble unsigned-int bug.	2026-04-30 17:12:25 +02:00
pstruebi	d2e47b79d9	Apply advertising TX power via Zephyr vendor-specific command for Nordic SDC.	2026-04-30 17:07:28 +02:00
pstruebi	bc8cd78c4a	implement changes for dynamic power setting	2026-04-30 13:47:40 +02:00