Stages#
Stages are ordered by the earliest point each can start, not a strict sequence; jobs overlap wherever the binary and library needs graphs allow. Signing covers the binary before archiving. Pull requests build and upload a workflow artifact; they skip signing, scanning and uploads.
From a commit to the people running it
Stages are ordered by the earliest point each can start; jobs overlap where the workflows' needs allow.
-
source
Source
Consumer Git state: pull request, main push, branch or tag. The consumer's caller workflow selects the events and pins the StroggForge ref.
-
tool
Toolchain
clang and lld matching rustc's LLVM major in every compiling job; EL9 builder images published separately for Linux and PortMaster.
-
boundary
Verify
One lint job (formatting, RustSec audit, MSRV, non-tag crates.io dry runs) and a test job per desktop platform, each running pedantic Clippy with every feature and with the features its release ships, then the tests. They run alongside the builds; publishing needs every one.
-
component
Build
Release binaries per platform: hosted desktop runners, the EL9 Linux container, and opt-in Android and PortMaster targets.
-
boundary
Sign
Keyless Cosign signature over the binary itself, before archiving. Pull requests skip it.
-
component
Package
Zip archive with the binary, its Cosign bundle and include files; VirusTotal scan; staged GitHub and Nexus workflow artifacts.
-
service
Publish
Refresh the GitHub Release boundary, then upload. Tagged runs publish crates, per package or as a dependency-ordered workspace.
-
component
Document
Rustdoc Pages on configured main pushes, after the gates. The changelog is uploaded by publish; benchmarks run on tags after it.
-
service
Distribute and announce
Configured AUR and Nexus uploads, dependent-repository update issues, and one aggregated Discord notification.
-
result
Callers
15 projects call StroggForge
How the pieces relate
- Source Toolchain
- Toolchain Verify
- Verify Build
- Build Sign
- Sign Package
- Package Publish
- Publish Document
- Document Distribute and announce
- Distribute and announce Callers
| # | Stage | Jobs and steps | What happens |
|---|---|---|---|
| 1 | Source | caller workflow | Consumer Git state: pull request, main push, branch or tag. The consumer's caller workflow selects the events and pins the StroggForge ref. |
| 2 | Toolchain | rust-setup: Install clang and lld matching rustc's LLVM publish-linux-x86_64-el9-builder: publish publish-portmaster-aarch64-el9-builder: publish | clang and lld matching rustc's LLVM major in every compiling job; EL9 builder images published separately for Linux and PortMaster. |
| 3 | Verify | rustGlobalBuild: lint, test libGlobalBuild: lint, test corprus-crucible: Lint the build as released | One lint job (formatting, RustSec audit, MSRV, non-tag crates.io dry runs) and a test job per desktop platform, each running pedantic Clippy with every feature and with the features its release ships, then the tests. They run alongside the builds; publishing needs every one. |
| 4 | Build | rustGlobalBuild: release, release-linux, release-android, release-portmaster corprus-crucible: Build Release | Release binaries per platform: hosted desktop runners, the EL9 Linux container, and opt-in Android and PortMaster targets. |
| 5 | Sign | corprus-crucible: Sign Binary | Keyless Cosign signature over the binary itself, before archiving. Pull requests skip it. |
| 6 | Package | corprus-crucible: Create Archive, VirusTotal Scan, Prepare GitHub Release Artifact, Prepare Nexus Mods Archive | Zip archive with the binary, its Cosign bundle and include files; VirusTotal scan; staged GitHub and Nexus workflow artifacts. |
| 7 | Publish | rustGlobalBuild: publish, crates libGlobalBuild: publish, crates | Refresh the GitHub Release boundary, then upload. Tagged runs publish crates, per package or as a dependency-ordered workspace. |
| 8 | Document | rustGlobalBuild: docs, benchmarks libGlobalBuild: docs, benchmarks | Rustdoc Pages on configured main pushes, after the gates. The changelog is uploaded by publish; benchmarks run on tags after it. |
| 9 | Distribute and announce | rustGlobalBuild: aur, nexus discord: discord-notify | Configured AUR and Nexus uploads, dependent-repository update issues, and one aggregated Discord notification. |
Callers#
- libGlobalBuild: dream_path / dream-path, dream_archive, vfstool_lib, openmw-config, L3i / l3i, dream-net, dream-soft-render
- modGlobalBuild: DreamWeave-Mod-Template, S3ctors-S3cret-St4sh / St4sh
- rustGlobalBuild: VFSTool, S3LightFixes, Morrobroom, greenmote, dream-ini, dream_archivetool
Boundaries#
StroggForge manufactures Rust components. The Mod Template provides the static docs shell. St4sh (with Cod3x) is the Lua(u)/OpenMW side; it and the Mod Template call only createRelease to refresh the release their static site uploads to. Libraries skip binary packaging and use the crate publication lane.