1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
# crates/assay — runtime binary (`assay-lua` on crates.io, `assay`
# installed). Owns the workspace-wide cargo tasks: cargo treats the
# workspace as one unit (single Cargo.lock, shared target/), so
# building / testing / clippy-ing this project is the same as doing it
# for every member crate. Per-crate moon.yml files (crates/assay-*)
# exist for the project graph, not for running cargo a second time.
language: "rust"
layer: "application"
stack: "systems"
fileGroups:
# Paths resolve relative to this file (crates/assay/moon.yml). Moon no
# longer accepts `..` parent-directory traversal, so cross-crate
# invalidation is expressed via `dependsOn` below (moon's
# affected-graph picks up changes in dependent projects
# automatically). Workspace-wide `cargo test --workspace` still
# exercises every crate regardless.
rust-sources:
- "src/**/*"
- "stdlib/**/*"
- "Cargo.toml"
dependsOn:
- "assay-domain"
- "assay-workflow"
- "assay-dashboard"
- "assay-auth"
- "assay-engine"
tasks:
lint:
command: "cargo clippy --workspace --tests -- -D warnings"
inputs:
- "@group(rust-sources)"
options:
cache: true
runInCI: true
build:
deps:
- "build-runtime"
# `cargo build --release` at workspace level builds libs but SKIPS
# any bin with `required-features` that aren't in the top-level
# feature set. `assay-engine` has `required-features = ["server"]`
# so the engine binary wasn't being built by the default command —
# downstream dashboard-e2e then failed with "target/release/
# assay-engine: No such file or directory". This task composes the
# CLI build with the engine binary build for full-stack e2e jobs.
command: "cargo build --release -p assay-engine --bin assay-engine"
inputs:
- "@group(rust-sources)"
options:
# Moon's task cache can't capture workspace-release outputs (target/
# lives outside this project, and `outputs:` forbids `..`). Cargo's
# incremental + Swatinem/rust-cache handle rebuild avoidance.
cache: false
runInCI: true
build-runtime:
# Sysops and site tasks only execute the Assay CLI; they should not
# build assay-engine just to run Lua-level checks.
command: "cargo build --release -p assay-lua --bin assay"
inputs:
- "@group(rust-sources)"
options:
# Moon's task cache can't capture workspace-release outputs (target/
# lives outside this project, and `outputs:` forbids `..`). Cargo's
# incremental + Swatinem/rust-cache handle rebuild avoidance.
cache: false
runInCI: true
test:
command: "cargo test --workspace"
inputs:
- "@group(rust-sources)"
- "tests/**/*"
options:
# Cross-crate test changes are picked up via `dependsOn` on the
# project itself — moon walks project deps for affected detection.
cache: true
runInCI: true
test-lua-stdlib:
# Fast gate for changes that only touch the Assay Lua stdlib tests.
# The full workspace test task remains the Rust/API gate; this keeps
# assertion-helper churn in tests/pkg_lua, tests/nspawn_lua, etc. from
# dispatching unrelated engine/dashboard checks.
command: "cargo test -p assay-lua --test stdlib_pkg --test stdlib_nspawn --test stdlib_rustic --test stdlib_fs_snapshot"
inputs:
- "stdlib/**/*"
- "tests/**/*_lua/**/*.lua"
- "tests/stdlib_pkg.rs"
- "tests/stdlib_nspawn.rs"
- "tests/stdlib_rustic.rs"
- "tests/stdlib_fs_snapshot.rs"
options:
cache: true
runInCI: true