Currently we run the job at midnight here and in `sepc256k1`, this led recently to one using the nightly toolchain from the 10th of Sep and the other using the toolchain from 11th of Sep. Update to run at 5 past so this doesn't happen again. |
||
|---|---|---|
| .. | ||
| README.md | ||
| cargo-semver-checks-version | ||
| coveralls.yml | ||
| cron-daily-fuzz.yml | ||
| cron-daily-kani.yml | ||
| cron-semi-weekly-update-nightly.yml | ||
| cron-weekly-rustfmt.yml | ||
| cron-weekly-update-cargo-semver-checks.yml | ||
| cron-weekly-update-stable.yml | ||
| gh-release.yml | ||
| manage-pr.yml | ||
| miri.yml | ||
| release.yml | ||
| rust.yml | ||
| semver-checks-pr-label.yml | ||
| semver-checks.yml | ||
| shellcheck.yml | ||
| stable-version | ||
README.md
rust-bitcoin workflow notes
We are attempting to run max 20 parallel jobs using GitHub actions (usage limit for free tier).
ref: https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration
The minimal/recent lock files are handled by CI (rust.yml).
Jobs
Run from rust.yml unless stated otherwise. Unfortunately we are now exceeding the 20 job target. (Prepare is quick and must be run first anyway.)
PrepareStable - minimalStable - recentNightly - minimalNightly - recentMSRV - minimalMSRV - recentLintDocsDocsrsBenchASANWASMArch32bitCrossEmbeddedKaniCoveralls- run bycoveralls.ymlrelease- run byrelease.ymllabeler- run bymanage-pr.ymlShellcheck- run byshellcheck.yml