A CI/CD template for Rust crates to test across multiple architectures and publish binary releases for Linux, macOS, and Windows.
Trust is a CI/CD template for Rust crates that automates testing across multiple architectures and operating systems, and publishes binary releases. It solves the problem of ensuring cross-platform compatibility and simplifying the distribution of pre-built binaries for Rust applications.
Rust developers and maintainers who need to test their crates on various platforms and distribute binary releases efficiently.
Developers choose Trust for its comprehensive cross-platform testing support, automated binary release publishing, and reusable configuration that reduces CI/CD setup time.
Travis CI and AppVeyor template to test your Rust crate on 5 architectures and publish binary releases of it for Linux, macOS and Windows
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Tests on over 20 targets including Android, iOS, and various Linux architectures, as detailed in the Supported targets section, ensuring broad compatibility.
Pushing an annotated tag triggers automatic publishing of binary releases for Linux, macOS, and Windows, streamlining deployment as described in the Generate binary releases section.
Caches and reuses Cargo artifacts between CI builds, reducing build times significantly, which is highlighted in the Features list.
Allows customization of test targets, Rust channels, and deploy conditions through TODO comments in config files, as noted in the How-to section.
Relies on Travis CI and AppVeyor, which are less commonly used today compared to GitHub Actions, limiting modern integration and potential support.
Requires copying and adjusting YAML files with TODO comments, not a seamless setup, as indicated in the 'Use this template' instructions.
Must be hosted on GitHub, as specified in Requirements, excluding projects on other version control platforms.
Upgrading the template involves checking versions, reviewing changelogs, and applying patches manually, which can be error-prone as explained in the upgrade section.