mod from_commit¶
- module from_commit¶
Classify easystack
from-commitpins against an EasyBuild release.stack from-commitreads easystacks, the documentsstack easystackwrites.recipe lintchecks.ebtext, and a pin is not recipe text, so the check is a stack subcommand. Containment is git merge-base –is-ancestor, the same question the reach and overlap tools ask of a commit and a ref: is this commit already in the release tag.Functions
- fn check(request: &FromCommitRequest) -> Result<FromCommitReport>¶
Classify every
from-commitandinclude-easyblocks-from-commitpin.Exit status is not applied here. The CLI exits 1 when
FromCommitReport::releasedis non-zero.unknownis a missing commit or a missing tag, never a guess.
Structs and Unions
- struct FromCommitReport¶
The report
stack from-commitprints.- stdout: String¶
CLI stdout, including the trailing newline.
- document: Value¶
The same report as JSON.
- released: usize¶
Pins whose commit is contained in the release tag.
- newer: usize¶
Pins whose commit is in the checkout and is not in the release tag.
- unknown: usize¶
Pins whose commit or release tag is missing from the checkout.
- rewritten: usize¶
Pins
--rewritedropped from the easystacks.
- struct FromCommitRequest¶
Arguments for
stack from-commit.- easystacks: Vec<PathBuf>¶
Easystack files, in report order.
- easyconfigs_repo: Option<PathBuf>¶
easybuild-easyconfigs checkout for
from-commitpins.
- easyblocks_repo: Option<PathBuf>¶
easybuild-easyblocks checkout for
include-easyblocks-from-commitpins.
- easybuild_version: Option<String>¶
Release
X.Y.Z. Overrideseb-X.Y.Zin each easystack file name.
- json: bool¶
Print the report as JSON.
- rewrite: bool¶
Drop each pin the release already carries with the same bytes, in place. A pin whose released file differs stays: it names the file that was installed, and the release would build a different one.