Detach fixture repository and document standalone use
Rust CI Cargo tests passed.
Gitea/rust_realease/pipeline/head This commit looks good
Details
Rust CI Cargo tests passed.
Gitea/rust_realease/pipeline/head This commit looks good
Details
This commit is contained in:
parent
fee72e258d
commit
7a1de6803c
|
|
@ -1,3 +0,0 @@
|
|||
[submodule "target_test_project"]
|
||||
path = target_test_project
|
||||
url = https://proxy.dandaedre.com/gitea/idle-org/target_test_project.git
|
||||
|
|
@ -100,6 +100,6 @@ cargo clippy --all-targets --all-features -- -D warnings
|
|||
cargo test --all
|
||||
```
|
||||
|
||||
Jenkins runs Cargo tests only. Cross builds and live Gitea releases are separate release checks. The small `target_test_project` submodule provides a fast target matrix fixture.
|
||||
Jenkins runs Cargo tests only. Cross builds and live Gitea releases are separate release checks. The small [target_test_project fixture](https://proxy.dandaedre.com/gitea/idle-org/target_test_project) is maintained in its own repository for fast target matrix experiments. Clone it separately when needed; it is not part of this checkout.
|
||||
|
||||
With `cargo-binstall` installed, run the opt-in isolated install fixture for all three targets with `cargo test real_binstall_installs_local_release_fixture -- --ignored`.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,16 @@
|
|||
# Advanced usage
|
||||
|
||||
## Disposable release fixture
|
||||
|
||||
The [target_test_project repository](https://proxy.dandaedre.com/gitea/idle-org/target_test_project) is a small standalone Cargo binary for Cross and Gitea integration tests. Clone it separately rather than expecting a submodule in this repository:
|
||||
|
||||
```bash
|
||||
git clone https://proxy.dandaedre.com/gitea/idle-org/target_test_project.git
|
||||
rust_realease ./target_test_project --dry-run
|
||||
```
|
||||
|
||||
Its public [v0.1.3 release](https://proxy.dandaedre.com/gitea/idle-org/target_test_project/releases/tag/v0.1.3) was used to validate preparation, all three default Cross targets, published checksums, and isolated cargo-binstall installs. Use a new version and tag for future publication tests; release assets with the same names are deliberately treated as collisions.
|
||||
|
||||
## Sources and package selection
|
||||
|
||||
`SOURCE` can be a local directory, an HTTP(S) Git URL, an SSH URL, or an SCP-style URL such as `git@host:owner/repo.git`. Remote sources are cloned into a managed checkout. Use `--keep-workdir` to retain that checkout and its artifacts; preparation retains remote checkouts automatically. Local sources are never deleted.
|
||||
|
|
|
|||
|
|
@ -1 +0,0 @@
|
|||
Subproject commit 0c6e30367b9861f870be057da18d11fe22895ddf
|
||||
Loading…
Reference in New Issue