forked from StudioInfinity/dyna3
Vectornaut
b86f176151
Adds a continuous integration workflow to the repository, using the [Forgejo Actions](https://forgejo.org/docs/next/user/actions/) framework. Concurrently, Aaron added a [wiki page](https://code.studioinfinity.org/glen/dyna3/wiki/Continuous-integration) to document the continuous integration system. In particular, this page explains how to [run continuous integration checks on a development machine](wiki/Continuous-integration#execution), either directly or in a container. Co-authored-by: Aaron Fenyes <aaron.fenyes@fareycircles.ooo> Co-authored-by: Glen Whitney <glen@studioinfinity.org> Reviewed-on: StudioInfinity/dyna3#75 Co-authored-by: Vectornaut <vectornaut@nobody@nowhere.net> Co-committed-by: Vectornaut <vectornaut@nobody@nowhere.net>
14 lines
No EOL
468 B
Rust
14 lines
No EOL
468 B
Rust
use std::process::Command;
|
|
|
|
// build and bundle the application, reporting success if there are no errors or
|
|
// warnings. to see this test fail while others succeed, try moving `index.html`
|
|
// or one of the assets that it links to
|
|
#[test]
|
|
fn trunk_build_test() {
|
|
let build_status = Command::new("trunk")
|
|
.arg("build")
|
|
.env("RUSTFLAGS", "-D warnings")
|
|
.status()
|
|
.expect("Call to Trunk failed");
|
|
assert!(build_status.success());
|
|
} |