bob-cli CI¶

The reusable CI workflow checks Rust code, scripts, and package contents on Linux and macOS. The release train calls it with full=true for the exact SHA it plans to release.

Triggers¶

CI runs on pushes to master and ci/** branches, pull requests, manual workflow dispatches, and workflow_call. Manual dispatch accepts full, a boolean that defaults to false. The release workflow passes the SHA and full=true through workflow_call.

Jobs¶

The lint job runs release-tool unit tests through check-release-tools. The package job uses Cargo package verification, checks that required notices are included, and keeps the archive below its size thresholds. CI does not run docs-check; the docs publishing pipeline owns that gate.

When full=true, Linux installs zsh, pandoc, poppler utilities, TeX packages, fonts, and other tools needed by tests that otherwise self-skip. A ci/full* push also enables this set of tools. macOS installs Bash 5 for tests that need it while preserving its native BSD utilities.

Measured GitHub job times¶

The CI phase measured these wall times on GitHub Actions:

Runner queues and cache state change these times; use them as a reference, not a service-level target.

Keep tests portable¶

Tests must not depend on a developer's HOME configuration, extra PATH tools, locale, or timezone. Give tests temporary configuration and directories, put any stub executable on a test-controlled PATH, and set an available UTF-8 locale or make text assertions locale-independent. Set TZ explicitly when a test depends on a date.

Run CI on a scratch branch¶

Push a ci/** branch to run the normal workflow without changing master. Use a branch starting with ci/full to run the extra Linux tools. Remove the scratch branch after review. For release workflow changes, use ci/release/**; those runs are always dry runs.

Related¶

• Release train reference
• Test release workflow changes
• Build the docs