eb-stack
0.7.4
eb-stack reads conda-forge, Spack, PyPI, CRAN, Cargo, LuaRocks, Raku, and EasyBuild recipes into one package plan, writes a planned CycloneDX SBOM and a Resolvo lock per profile, emits one conventional easyconfig per profile, and drives those recipes through a persisted build campaign.
eb-stack¶
Version 0.7.4 is the crates.io package and the GitHub release. package plan and package bump establish resolves. campaign run establishes builds and binary-verified.
Inspect a bundled recipe, split a build list, and see exit 78.
Release archives for Linux, macOS, and Windows, plus crates.io and a checkout.
Plan conda-forge eOn and drive a target campaign.
How a build list becomes shards, and when a lane is refused.
Task pages for build lists, bumps, campaigns, and site checks. The sidebar lists every guide.
Flags, exit statuses, and the Rust API.
Toolchain, tests, and how the manual is built.
Release notes from 0.3.0 through 0.7.4.
How-To Guides
- Run an annual toolchain-generation bump
- Author a new package from conda-forge or Spack
- Site Python extras on EESSI
- Site R extras on EESSI
- eOn on EESSI with EESSI-extend and eb –robot
- Spack on EESSI with EESSI installs as externals
- Repair a failed campaign
- Solve a consistent stack lock
- Classify a site module list
- Emit a build list and stack diff
- Bump an existing EasyBuild recipe
- Declare root priority for multi-root optimization
- Which easyconfigs an easyblock change reaches
- Find shared builds across open pull requests
- Find open easybuild-easyconfigs pull requests that add the same software
- What an in-place patch forces EESSI to rebuild
- Which modules carry a component, and what that forces rebuilt
- Find from-commit pins an EasyBuild release already contains
- Refuse a plan an architecture cannot build
- Find a missing patch before the bot does
- Refuse entries outside the EESSI version’s generations
- Fail a build list that names software the baseline provides
- Route the modules a stack does not have
- Check CUDA compute capabilities in an easystack plan
- Warn about known per-architecture failures
- Warn before a bot job runs out of memory
- Read an EESSI bot FAILURE
- Split a Jenkins build list into shards
- Plan software-layer pull requests that do not overlap
- Regroup a Jenkins build list under the previous sections
- Write an easystack from a stack lock
- Read the easyblock, templates, and hierarchy
- Report the newest stable upstream release
- Read the reproduction scoreboard
- Report a site recipe that shadows an EESSI module
Reference
Topics
Project
Why¶
Claim ladder: package plan and package bump establish resolves. campaign run establishes builds and binary-verified.¶
A site that rebuilds an EESSI or EasyBuild generation keeps the dependency
lock, the EasyBuild run, and the checks after install as separate records.
eb-stack names those records resolves, builds, and binary-verified.
package plan and package bump establish resolves. campaign run
establishes the other two. The campaign JSON spells the third claim
binary_verified. Closure, generation, baseline, toolchain family, and
reachability are in the glossary.
The same plan feeds a Jenkins build list. stack shard splits the list
into jobs that can run together, and stack admit exits 78 when the
scratch inode quota cannot hold the next lane. That model is
Sharding and inode admission.
EasyBuild still performs the build and the install. eb-stack routes
eb --robot through a configured target. The emitted SBOM is the planned
inventory; binary verification is the campaign claim that runs after install.
The dependency domain is EasyBuild’s name / version / toolchain /
dependencies shape. Preferences for a distribution or a site are inputs
to Resolvo.
Who it is for¶
Site administrators building a stack start with
Installation and Get started,
then the how-to guides in the sidebar (annual bump, new package, shard,
campaign repair). The GitHub release is 0.7.4, with archives for Linux
(x86-64, aarch64), macOS, and Windows. cargo install eb_stack --locked
builds that same 0.7.4 from crates.io. eb-stack --version prints
eb-stack 0.7.4.
Contributors start at Contributing: Rust 1.90,
cargo test --locked, and the Org-to-Sphinx build. The generated Rust API
is the Rust API page.
Where to go¶
Get started: inspect, shard, and exit 78 on the bundled fixtures.
Installation: per-platform release archives, crates.io, and a checkout.
Tutorial: conda-forge eOn through a target campaign.
Annual bump and a new package.
CLI, Model Context Protocol server, package bundles, build targets, campaign state.
From recipe to verified package and what a dependency closure answers.
Contributing and Changelog.
Citation¶
For unreleased source, cite the repository revision you used. The CITATION.cff file provides structured author and project metadata.
Rohit Goswami, eb-stack (source revision <commit>), https://github.com/stackhands/eb-stack
License¶
MIT License. See LICENSE in the repository.
Discovery¶
llms.txt indexes this manual. llms-full.txt repeats every page in one file. Contributing describes contribution and validation requirements. The skills for inspect, plan, bump, a stack SBOM, pull-request overlap, and the stdio server are under skills/. The Model Context Protocol manifest is server.json. Client configuration is the server page.
Build these docs¶
cd eb-stack
pixi run -e docs docbld
# HTML -> docs/build/index.html
Org sources live under docs/orgmode/; Emacs ox-rst publishes to
docs/source/; Sphinx + Shibuya builds the site.