yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

CI gate on Gitea Actions #2

New Issue
Closed
opened 2026-08-22 18:22:38 +01:00 by naps62-yolo · 1 comment
naps62-yolo commented 2026-08-22 18:22:38 +01:00
Owner
Copy Link
Copy Source

Implement the per-push gate from DESIGN.md §12.

Steps: cargo fmt --check, cargo clippy --all-targets -- -D warnings,
cargo machete, cargo nextest run, and for the frontend biome ci web/ plus
tsc -b --noEmit.

Total wall-clock is an explicit constraint, so:

  • Cache ~/.cargo/registry, ~/.cargo/git and target/, keyed on
    Cargo.lock plus rust-toolchain.toml.
  • Never build --release in the gate.
  • cargo deny goes on a schedule, not on push.
  • E2E is a separate job, main and PRs touching those crates only.

Acceptance: gate is green and under five minutes warm. Record the cold and warm
times on the issue — later issues will be judged against them.

Depends on: #1

Labels: phase/1-skeleton, area/ci, difficulty/moderate, type/chore

Implement the per-push gate from `DESIGN.md` §12. Steps: `cargo fmt --check`, `cargo clippy --all-targets -- -D warnings`, `cargo machete`, `cargo nextest run`, and for the frontend `biome ci web/` plus `tsc -b --noEmit`. Total wall-clock is an explicit constraint, so: - Cache `~/.cargo/registry`, `~/.cargo/git` and `target/`, keyed on `Cargo.lock` plus `rust-toolchain.toml`. - Never build `--release` in the gate. - `cargo deny` goes on a schedule, not on push. - E2E is a separate job, `main` and PRs touching those crates only. Acceptance: gate is green and under five minutes warm. Record the cold and warm times on the issue — later issues will be judged against them. --- **Depends on:** #1 Labels: `phase/1-skeleton`, `area/ci`, `difficulty/moderate`, `type/chore`
naps62-yolo added the area/cidifficulty/moderatephase/1-skeletontype/chore labels 2026-08-22 18:22:38 +01:00
naps62-yolo commented 2026-08-22 19:25:25 +01:00
Author
Owner
Copy Link
Copy Source

Done in bbe53ba and 86f6ed4, direct to `main` (no PR — bootstrap).

Three workflows: `ci.yml` (per-push gate), `e2e.yml` (main plus PRs touching the crates whose seams it covers), `audit.yml` (`cargo deny`, weekly). `deny.toml` included.

Timings, as this issue asked for. Budget is five minutes.

Job Cold Warm
rust 65s 21s
web 6s 5s
e2e 40s 30s

Cold is the whole gate from an empty cache, so there is a lot of headroom for real tests and the frontend.

Notes:

  • `cargo-nextest` comes from the prebuilt binary at `get.nexte.st`; `cargo install` from source costs minutes.
  • Cache covers `~/.cargo/{bin,registry,git}` and `target/`, keyed on `Cargo.lock` plus `rust-toolchain.toml`. Nothing builds `--release`.
  • The first e2e run failed only on the empty test crate. Everything before it worked, including pulling and starting the Transmission service container — which is what the e2e harness issue depends on.
Done in bbe53ba and 86f6ed4, direct to \`main\` (no PR — bootstrap). Three workflows: \`ci.yml\` (per-push gate), \`e2e.yml\` (main plus PRs touching the crates whose seams it covers), \`audit.yml\` (\`cargo deny\`, weekly). \`deny.toml\` included. **Timings, as this issue asked for.** Budget is five minutes. | Job | Cold | Warm | |---|---|---| | rust | 65s | 21s | | web | 6s | 5s | | e2e | 40s | 30s | Cold is the whole gate from an empty cache, so there is a lot of headroom for real tests and the frontend. Notes: - \`cargo-nextest\` comes from the prebuilt binary at \`get.nexte.st\`; \`cargo install\` from source costs minutes. - Cache covers \`~/.cargo/{bin,registry,git}\` and \`target/\`, keyed on \`Cargo.lock\` plus \`rust-toolchain.toml\`. Nothing builds \`--release\`. - The first e2e run failed only on the empty test crate. Everything before it worked, including pulling and starting the Transmission service container — which is what the e2e harness issue depends on.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No Label area/ci difficulty/moderate phase/1-skeleton type/chore
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: yolo/arr#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?