robert/PedalPebble
Watch
1
0
Fork
You've already forked PedalPebble
 0
Code Issues 43 Pull requests Projects Releases 1 Packages Wiki Activity Actions

CI: JVM tests, host C tests and both watchapp builds on every push #67

New issue
Closed
opened 2026-09-01 17:35:45 +02:00 by robert · 2 comments
robert commented 2026-09-01 17:35:45 +02:00 (Migrated from git.butzei.de)
Copy link

Goal

Run the tests on every push. NFR-C7 was filed as "Open - recommended"; it is the cheapest quality win in the plan and it protects the fixture suites that #38 and #39 build.

Acceptance criteria

  • CI runs on every push and every pull request
  • JVM unit tests for the companion (#22, #39, #65)
  • Host-compiled watchapp logic tests (#68)
  • pebble build for both emery and gabbro, failing on warnings that matter
  • Android assemble, so a broken Gradle setup is caught before a ride
  • Enrichment fixtures (#38) run without network and without BRouter installed
  • Build status visible on the repository
  • Runtime kept short enough that it is not routinely skipped - target under 10 minutes
  • No secrets required for any CI job; anything needing a key is skipped with a clear message, per NFR-S3

Files

  • .gitea/workflows/ci.yml

Notes

See D34. The watchapp build matters as much as the tests: three screen geometries and a lot of PBL_IF_ROUND_ELSE, and a build that only ever runs on one developer's machine will break on the other platform quietly.

Update — 2026-09-03: the lanes and the runner

This issue now owns more than "CI runs tests" — it owns the whole pipeline defined in
PROCESS.md and
TESTING.md:

  • Self-hosted runner: an act_runner in Docker on the development machine, registered
    against this Forgejo instance, with a label matching the workflows. Nobody else owns this;
    without it nothing in this issue is testable
  • Two lanes, decoupled: dev-artifact (debug .pbw + .apk, published on every push, waits
    for no test — the 5-minute path) runs in parallel with the fast lane (target 120 s, hard fail
    180 s). Release tags refuse artifacts not built by the tag pipeline
  • Pinned toolchain images: Pebble build image pins pebble-tool / SDK 4.33.1 with the
    Python 3.13 pin asserted (3.14 installs but breaks pebble build — D54); Android image
    pins JDK 21 and a Gradle cache warmed at image build time
  • Workflow files live in .forgejo/workflows/ (Forgejo, not .gitea/ — verify which this
    instance honours, and note it here)
  • Artifact delivery Robert can reach from his phone: a rolling pre-release with the .pbw
    and debug .apk attached, so the 5-minute promise ends at his phone's browser, not at an API
    token

The 10-minute target above is superseded by the lane budgets in PROCESS.md §1.

## Goal Run the tests on every push. NFR-C7 was filed as "Open - recommended"; it is the cheapest quality win in the plan and it protects the fixture suites that #38 and #39 build. ## Acceptance criteria - [ ] CI runs on every push and every pull request - [ ] JVM unit tests for the companion (#22, #39, #65) - [ ] Host-compiled watchapp logic tests (#68) - [ ] `pebble build` for **both** `emery` and `gabbro`, failing on warnings that matter - [ ] Android assemble, so a broken Gradle setup is caught before a ride - [ ] Enrichment fixtures (#38) run without network and without BRouter installed - [ ] Build status visible on the repository - [ ] Runtime kept short enough that it is not routinely skipped - target under 10 minutes - [ ] No secrets required for any CI job; anything needing a key is skipped with a clear message, per NFR-S3 ## Files - `.gitea/workflows/ci.yml` ## Notes See D34. The watchapp build matters as much as the tests: three screen geometries and a lot of `PBL_IF_ROUND_ELSE`, and a build that only ever runs on one developer's machine will break on the other platform quietly. ## Update — 2026-09-03: the lanes and the runner This issue now owns more than "CI runs tests" — it owns the whole pipeline defined in [PROCESS.md](https://git.butzei.de/robert/PedalPebble/src/branch/main/docs/PROCESS.md) and [TESTING.md](https://git.butzei.de/robert/PedalPebble/src/branch/main/docs/TESTING.md): - [ ] **Self-hosted runner**: an `act_runner` in Docker on the development machine, registered against this Forgejo instance, with a label matching the workflows. Nobody else owns this; without it nothing in this issue is testable - [ ] **Two lanes, decoupled**: `dev-artifact` (debug `.pbw` + `.apk`, published on every push, waits for no test — the 5-minute path) runs in parallel with the fast lane (target 120 s, hard fail 180 s). Release tags refuse artifacts not built by the tag pipeline - [ ] **Pinned toolchain images**: Pebble build image pins `pebble-tool` / SDK 4.33.1 with the **Python 3.13 pin asserted** (3.14 installs but breaks `pebble build` — D54); Android image pins JDK 21 and a Gradle cache warmed at image build time - [ ] Workflow files live in `.forgejo/workflows/` (Forgejo, not `.gitea/` — verify which this instance honours, and note it here) - [ ] **Artifact delivery Robert can reach from his phone**: a rolling pre-release with the `.pbw` and debug `.apk` attached, so the 5-minute promise ends at his phone's browser, not at an API token The 10-minute target above is superseded by the lane budgets in PROCESS.md §1.
robert commented 2026-09-04 00:35:33 +02:00
Owner
Copy link

Workflow directory, verified: .forgejo/workflows/, not .gitea/workflows/.

Checked against https://forgejo.org/docs/latest/user/actions/overview/ on 2026-09-04: .forgejo/workflows/ is the primary location, and the only documented fallback (used when that directory is absent) is .github/workflows/. Forgejo's own docs never mention .gitea/workflows/ as a recognised path at all — it isn't a secondary option, it simply doesn't work on this instance (16.0.3+gitea-1.22.0). So the original issue text ("Files: .gitea/workflows/ci.yml") was wrong, most likely a holdover from before this Forgejo version was confirmed; the 2026-09-03 update's .forgejo/workflows/ is correct.

PR #80 implements the four lanes (dev-artifact/fast/slow/tag) from PROCESS.md/TESTING.md under .forgejo/workflows/, plus the three pinned toolchain images and docs/CI.md. Runner registration is deliberately excluded from that PR — it needs a token from the web UI and is Robert's manual step, not something this session attempted or should attempt. Everything else is workflow-definition work, verified by reading current Forgejo docs rather than by execution (no runner exists yet to run it against), and the PR says so plainly. See PR #80 for the full breakdown of what's real vs. what's flagged as unverified.

**Workflow directory, verified:** `.forgejo/workflows/`, not `.gitea/workflows/`. Checked against <https://forgejo.org/docs/latest/user/actions/overview/> on 2026-09-04: `.forgejo/workflows/` is the primary location, and the *only* documented fallback (used when that directory is absent) is `.github/workflows/`. Forgejo's own docs never mention `.gitea/workflows/` as a recognised path at all — it isn't a secondary option, it simply doesn't work on this instance (16.0.3+gitea-1.22.0). So the original issue text ("Files: `.gitea/workflows/ci.yml`") was wrong, most likely a holdover from before this Forgejo version was confirmed; the 2026-09-03 update's `.forgejo/workflows/` is correct. PR #80 implements the four lanes (dev-artifact/fast/slow/tag) from PROCESS.md/TESTING.md under `.forgejo/workflows/`, plus the three pinned toolchain images and `docs/CI.md`. **Runner registration is deliberately excluded from that PR** — it needs a token from the web UI and is Robert's manual step, not something this session attempted or should attempt. Everything else is workflow-definition work, verified by reading current Forgejo docs rather than by execution (no runner exists yet to run it against), and the PR says so plainly. See PR #80 for the full breakdown of what's real vs. what's flagged as unverified.
robert commented 2026-09-04 00:37:07 +02:00
Owner
Copy link

Closed by PR #80 (merged): all four workflow files in .forgejo/workflows/ (verified against Forgejo docs — .gitea/workflows/ was never a real fallback, only .github/workflows/ is), pinned+self-verifying toolchain Dockerfiles under tooling/docker/, and docs/CI.md mapping PROCESS.md/TESTING.md onto the actual files. Untested by execution — no runner is registered on this instance yet, so nothing here has actually run. Explicitly out of scope by design: building/pushing the toolchain images and registering the act_runner, both left as Robert's manual steps. Give the workflow files an extra-careful read once a runner exists and the first real run happens.

Closed by PR #80 (merged): all four workflow files in `.forgejo/workflows/` (verified against Forgejo docs — `.gitea/workflows/` was never a real fallback, only `.github/workflows/` is), pinned+self-verifying toolchain Dockerfiles under `tooling/docker/`, and docs/CI.md mapping PROCESS.md/TESTING.md onto the actual files. **Untested by execution** — no runner is registered on this instance yet, so nothing here has actually run. Explicitly out of scope by design: building/pushing the toolchain images and registering the act_runner, both left as Robert's manual steps. Give the workflow files an extra-careful read once a runner exists and the first real run happens.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
area/gpx-cue-enricher-d59
area/round-display-support
area/rejoin-point-selection
area/digit-height-content-aware
area/geometry-enricher
area/page-template-hero1-grid6
area/nav-engine
area/cue-sheet-review
area/map-viewport-geometry
area/navigation-snapping-test-audit
area/lap-function
area/navigation-snapping
area/ble-power-meter
area/gpx-export
area/gpx-recording
area/pkjs-speed-feed
tooling/watchapp-distribution
area/csc-cadence
area/about-screen
area/backlight-policy
tooling/gpx-replay
area/derived-metrics
area/speed-pipeline-coverage-audit
area/speed-source-arbitration
area/speed-pipeline
area/stop-detector
area/ble-csc-sensor
area/persist-ride-state
area/foreground-location-service
area/protocol-version-handshake
area/real-komoot-fixture
tooling/message-keys-codegen
tooling/fix-android-platform-doc
area/settings-screen
tooling/first-real-android-build
tooling/fix-runner-label
area/cue-sheet-cache
area/route-library
area/page-template-renderer
area/colour-palette
area/page-carousel
area/ride-state-machine
area/watchapp-skeleton
tooling/host-test-harness
area/field-store-page-descriptors
tooling/ci-pipeline
area/cue-sheet-enricher-interface
area/gpx-share-import
process/security-persona
area/android-companion-skeleton
tooling/pebble-sdk-emulators
process/team-and-pipeline
dev-latest
v0.5.0
Labels
Clear labels   
area:companion
Android companion app

  
area:docs
Documentation

  
area:shared
Message contract shared by both sides

  
area:tooling
Build tooling, SDK, dev scripts

  
area:watchapp
Pebble C watchapp

  
blocker
Blocks a large part of the project until resolved

  
kind:chore
Setup, scaffolding, maintenance

  
kind:feature
New functionality

  
kind:spike
Time-boxed investigation to de-risk a decision

  
kind:test
Tests and fixtures

No labels
area:companion
area:docs
area:shared
area:tooling
area:watchapp
blocker
kind:chore
kind:feature
kind:spike
kind:test
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#2 Install Pebble SDK toolchain, build and run on the emery and gabbro emulators
robert/PedalPebble
#14 Android project skeleton and Gradle setup
robert/PedalPebble
Reference
robert/PedalPebble#67
No description provided.