diff --git a/docs/models/build_a_model/build_source_code.md b/docs/models/build_a_model/build_source_code.md index d40bdf94f..de94d3de0 100644 --- a/docs/models/build_a_model/build_source_code.md +++ b/docs/models/build_a_model/build_source_code.md @@ -29,8 +29,6 @@ As an example, in the following instructions we will show how to modify [MOM5 co !!! tip The following instructions are valid (with simple tweaks) for all [ACCESS models]. -## Prerequisites - - **NCI account**
Before building a model, you need to [Set Up your NCI Account](/getting_started/set_up_nci_account). @@ -127,6 +125,11 @@ spack concretize -f --reuse-deps spack concretize -f --fresh ``` + The version of [`access-nri/access-spack-packages`](https://github.com/ACCESS-NRI/access-spack-packages) must be compatible with the environment. If there are concretization errors try checking the version you cloned is the same as the version used in the deployment repository. + +## Prerequisites + + spack concretize -f --reuse-deps diff --git a/docs/models/build_a_model/create_a_prerelease.md b/docs/models/build_a_model/create_a_prerelease.md index 5ce72f99f..03a2b2dda 100644 --- a/docs/models/build_a_model/create_a_prerelease.md +++ b/docs/models/build_a_model/create_a_prerelease.md @@ -54,6 +54,10 @@ For more information on the `spack.yaml` file, refer to [ACCESS-NRI's DevDocs]( The `config` directory contains a single `versions.json` file. This file allows customisation of both the version of [`access-nri/spack`](https://github.com/ACCESS-NRI/spack) used to deploy the model and the version of [`access-nri/spack-packages`](https://github.com/ACCESS-NRI/spack-packages) that will source the recipes for the _Spack_ packages. + !!! warning + It is important that the version of [`access-nri/spack-packages`](https://github.com/ACCESS-NRI/spack-packages) is compatible with the environment. + If there are concretization errors try checking this. + ## Trigger model prerelease and release build deployments As mentioned above, prerelease build deployments are triggered by a push of one or more commits within a model deployment repository's open PR. When the PR is merged, a release build deployment is created.