balatro-seed-search/docs/development.md

3.4 KiB

Development and releases

Commands in this document run from the repository root and require a current stable Rust toolchain.

Quality checks

export RUSTUP_TOOLCHAIN=stable
cargo test --release --all-targets --locked
cargo clippy --all-targets --locked -- -D warnings
cargo run --release --example verify -- 100000
cargo run --release --example bench_throughput

The verifier checks deterministic engine invariants and published-pool sanity; it is not a complete external Balatro oracle. The benchmark covers joker, boss, voucher, tag, pack, and mixed filters. Measured scaling and optimization notes are in PERFORMANCE.md.

Repository-specific working rules and the commit-per-task policy are in AGENT.md. Current and planned work is tracked in TASK.md.

Releases

This repository follows the rust_realease contract. Preview the release plan without building or contacting Gitea:

rust_realease . --dry-run

The package version must match an existing local and remote vVERSION tag for publication. Cross and a Docker- or Podman-compatible backend build the targets declared in rust-release.toml:

  • x86_64-unknown-linux-musl;
  • aarch64-unknown-linux-musl; and
  • x86_64-pc-windows-gnu.

cargo-binstall packages and verifies the archives. Publish with a Gitea token from GITEA_TOKEN or an explicit token file:

rust_realease . --token-file ../gitea_token.txt

After a tagged release is published, cargo-binstall can use its matching native archive from the canonical repository:

cargo binstall --git \
  https://proxy.dandaedre.com/gitea/MadGobblins/balatro-seed-search \
  balatro-seed-search

The target images and environment passthrough are defined in Cross.toml.

Jenkins CI

Jenkinsfile runs the documented release tests, strict Clippy checks, the 100,000-seed engine verifier, and the native release build. Every successful branch build archives and fingerprints this file:

target/release/balatro-seed-search

The pipeline uses agent any because this repository has no confirmed installation-specific worker label. The selected worker must provide a POSIX shell, Git, and a current stable Rust toolchain with Cargo and Clippy. It must also be able to obtain the locked Cargo dependencies when they are not already cached. The toolchain stage fails with a direct error when a required command is missing; it does not install or update worker tools.

Run the Jenkins gates locally with:

export RUSTUP_TOOLCHAIN=stable
cargo test --release --all-targets --locked
cargo clippy --all-targets --locked -- -D warnings
cargo run --release --locked --example verify -- 100000
cargo build --release --locked --bin balatro-seed-search
test -s target/release/balatro-seed-search

This job does not publish releases or copy files to a shared destination on any branch. It requires no Jenkins credentials. Releases remain the explicit rust_realease workflow documented above.

For automatic Gitea builds, configure the canonical repository's webhook to the Jenkins installation's gitea-webhook/post endpoint and create a multibranch Pipeline job that reads Jenkinsfile. The installation must expose the publishChecks step for Gitea status reporting. Check-reporting errors are logged without replacing the original build result.