30bdf05f78
doc: Clarify the destination of checkout, remove investigative steps
/ test (pull_request) Successful in 2m17s
2025-04-02 13:20:34 -07:00
d768a39c7a
test: oops examine directories better
/ test (pull_request) Successful in 2m15s
2025-04-02 13:08:03 -07:00
17fc7265a2
test: revert intentional failure; examine directories
/ test (pull_request) Successful in 2m26s
2025-04-02 13:01:20 -07:00
Aaron Fenyes
3f4fe582b3
Fail CI to confirm that merging is blocked
/ test (pull_request) Failing after 1m8s
2025-04-02 12:40:30 -07:00
Aaron Fenyes
440b1dfb3d
Clarify where setup-trunk puts the Trunk binary
/ test (pull_request) Successful in 2m22s
2025-04-02 12:30:55 -07:00
Aaron Fenyes
efb2d39042
Clarify where stuff happens in the CI workflow
2025-04-02 12:06:01 -07:00
0e38a38b57
chore: remove now-useless /home/glen/.venv/bin:/home/glen/.elan/bin:/home/glen/.local/share/pnpm:/home/glen/.local/bin:/home/glen/bin:/usr/local/bin:/usr/bin:/bin:/snap/bin checks
/ test (pull_request) Successful in 2m23s
2025-04-01 19:51:07 -07:00
5e441d6b11
test: try $GITHUB_PATH for updating PATH
/ test (pull_request) Successful in 2m21s
2025-04-01 19:43:53 -07:00
80a4acd56a
test: check path at end of setup-trunk
/ test (pull_request) Failing after 1m21s
2025-04-01 19:23:39 -07:00
81035270b8
test: check path after setup-trunk
/ test (pull_request) Failing after 1m18s
2025-04-01 19:09:24 -07:00
4bb0b05635
test: move trunk installation for CI to ci-bin/
/ test (pull_request) Failing after 1m17s
2025-04-01 19:01:21 -07:00
Aaron Fenyes
df2d45816c
Find the home directory instead of hard-coding it
...
/ test (pull_request) Successful in 2m19s
This should make the `setup-trunk` workflow more container-independent.
2025-03-30 13:05:20 -07:00
Aaron Fenyes
992fb76419
Do the Trunk build check as an end-to-end test
...
/ test (pull_request) Successful in 2m18s
This consolidates our whole CI workflow into `cargo test`.
2025-03-28 12:30:02 -07:00
Aaron Fenyes
0a9d234557
Run the examples as tests
/ build (pull_request) Successful in 1m17s
/ test (pull_request) Successful in 1m8s
2025-03-28 00:36:38 -07:00
Aaron Fenyes
7f45e98b46
Switch to CircleCI's Rust + Node container image
...
/ build (pull_request) Successful in 2m24s
/ test (pull_request) Successful in 1m8s
/ run-examples (pull_request) Successful in 1m3s
This should make the `checkout` work on the runner host.
2025-03-27 22:19:54 -07:00
Aaron Fenyes
4251242953
Run CI on a stock image, installing Trunk by hand
...
/ build (pull_request) Failing after 4s
/ test (pull_request) Failing after 3s
/ run-examples (pull_request) Failing after 4s
Instead of building a custom CI image with Trunk pre-installed, let's
try running CI on a stock image, installing Trunk from a binary on every
workflow run.
2025-03-27 20:46:02 -07:00
Aaron Fenyes
f212cfadf4
Tell Docker to build Trunk with only one job
...
/ setup-image (pull_request) Failing after 23m14s
/ build (pull_request) Has been cancelled
/ test (pull_request) Has been cancelled
/ run-examples (pull_request) Has been cancelled
This might reduce the amount of memory it takes to build the CI image.
2025-03-27 18:28:17 -07:00
Aaron Fenyes
15375dc932
Remove the CI image setup script
...
/ setup-image (pull_request) Failing after 23m20s
/ build (pull_request) Has been cancelled
/ test (pull_request) Has been cancelled
/ run-examples (pull_request) Has been cancelled
The CI workflow now builds and tags the CI image automatically, so we
don't need the manual setup script anymore.
2025-03-26 02:32:25 -07:00
Aaron Fenyes
5f45c9c7a4
Set up the CI image during the CI workflow
2025-03-26 02:12:05 -07:00
Aaron Fenyes
71f4cd184c
Fail continuous integration on warnings
/ build (pull_request) Failing after 1s
/ test (pull_request) Failing after 1s
/ run-examples (pull_request) Failing after 1s
2025-03-12 15:44:43 -07:00
Aaron Fenyes
4442dd860b
Run continuous integration on a custom image
...
Write a Dockerfile that describes a Debian image with our build
environment set up in it. Write a script that builds and tags the custom
image. Set the continuous integration workflow to run on the custom
image, pulled from Docker's local image store.
Running the examples on the custom image takes the same steps as running
them on a development machine, so we no longer gain anything from
factoring out the `cargo run --example` steps. That means we can get rid
of the `run-examples` action. Since the build environment is now set up
ahead of time, we can get rid of the `setup-rust` action too.
2025-03-12 15:44:43 -07:00
Aaron Fenyes
bbfdf2b87f
Prototype a continuous integration workflow
...
This workflow is too spendthrift for deployment: every job sets up Rust,
and the `build` job also installs Trunk, which takes even more
resources. The workflow serves well, however, as a proof of concept.
Introducing a syntax error into `src/main.rs` causes the `build` and
`test` jobs to fail, but allows `run-examples` to succeed. Similarly,
introducing a syntax error into `examples/point-on-sphere.rs` causes
`run-examples` to fail, but allows the other jobs to succeed.
2025-03-12 15:44:43 -07:00
Aaron Fenyes
d243f19e25
Start tracking Cargo.lock
2025-03-12 15:44:43 -07:00
