Skip to content

Utilize train-specific artifacts - #154

Draft
msarahan wants to merge 1 commit into
rapidsai:mainfrom
msarahan:codex/unmodified-workflow-pilot
Draft

msarahan wants to merge 1 commit into
rapidsai:mainfrom
msarahan:codex/unmodified-workflow-pilot

Conversation

@msarahan

Copy link
Copy Markdown
Contributor

One of our goals in the new build system is to avoid depending on any external artifacts, aside from our stated inputs. These can come in a few different ways: remote conda content, remote pypi content, CPM/rapids-cmake.

This PR glues together settings and arguments to guide our build tools to our train-specific internal builds.

Keep release outputs and their evidence immutable and scoped to a frozen train instead of relying on ordinary CI publication or selecting the newest artifacts. Add private content bundles, train membership records, build-input identity and reuse, and prerequisite selection through isolated Conda and wheel views.

Pin build implementations and RAPIDS CMake, apply repository-specific locks and recipe constraints, and stage candidate documentation privately. Preserve the standard catalog action and upload contract alongside the candidate-specific storage path, including matrix and CUDA compatibility metadata.

Resolve train metadata from exact controller run bindings so standard project callers need no new inputs. Reject mismatched identities and unenrolled custom jobs, bound missing-record retries, and add schema, storage, dependency and run-binding checks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant