-
Notifications
You must be signed in to change notification settings - Fork 1
v6 Rollout #311
Copy link
Copy link
Closed
Labels
for:v6Applies to v6Applies to v6type:enhancementImprovements to existing featuresImprovements to existing featuresversion:MAJORRequires an update to Model Deployment Repositories CIRequires an update to Model Deployment Repositories CI
Metadata
Metadata
Assignees
Labels
for:v6Applies to v6Applies to v6type:enhancementImprovements to existing featuresImprovements to existing featuresversion:MAJORRequires an update to Model Deployment Repositories CIRequires an update to Model Deployment Repositories CI
References PR #306
Background
This issue serves as a progress-tracker for rolling out the new major version
build-cd v6.Generally, the changes for MDRs:
spack.modulessection is no longer required as it is injected at build-time. Users can still override it.spack-manifest-schema-version,config-versions-schema-versionandconfig-packages-schema-version. There is also a new, optional inputspack-manifest-schema-paththat defaults to the usual schema.config/packages.jsonfile that specifies special packages - ones for the release database, and another for module includes.github/CODEOWNERSfile that means any modification to.githubneeds to be reviewed by @CodeGat. It can be overridden by repository admins.vars.*_SCHEMA_VERSION,vars.BUILD_DB_PACKAGESonce this is merged.Note
Don't forget to do
model-tools,system-tools,model-deployment-template,software-deployment-templatespecially!