# Building from UM7 repo

**URL:** <https://forum.access-hive.org.au/t/building-from-um7-repo/3815>\
**Category:** General\
**Tags:** spack, help, um\
**Created:** [22 October 2024 02:35 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815 "2024-10-22T02:35:18Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![Jhan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/jhan/32/721_2.png) [@Jhan](https://forum.access-hive.org.au/u/Jhan)\
**Post date:** [23 October 2024 00:01 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/21 "2024-10-23T00:01:32Z")

</div>

Nope. Forbidden

---

<div class="post-metadata">

**Author:** ![harshula](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/harshula/32/256_2.png) [@harshula](https://forum.access-hive.org.au/u/harshula)\
**Post date:** [23 October 2024 00:29 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/22 "2024-10-23T00:29:41Z")

</div>

Hi @Jhan, Sounds good. Let’s meet at 1pm. I’ll send the Zoom link via a private message.

---

<div class="post-metadata">

**Author:** ![atteggiani](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/atteggiani/32/212_2.png) [@atteggiani](https://forum.access-hive.org.au/u/atteggiani)\
**Post date:** [23 October 2024 02:16 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/23 "2024-10-23T02:16:55Z")

</div>

> [@anton](#):
>
> @harshula - I think these [instructions](https://access-hive.org.au/models/run-a-model/build_a_model/#case1) have the arguments in the wrong order ?

Yes, you are right.

Will update the instructions.  
Thank you for finding out!

---

<div class="post-metadata">

**Author:** ![harshula](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/harshula/32/256_2.png) [@harshula](https://forum.access-hive.org.au/u/harshula)\
**Post date:** [23 October 2024 10:18 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/24 "2024-10-23T10:18:47Z")

</div>

Jhan created a Pre-release build that’s available for testing: [Update cable3 by JhanSrbinovsky · Pull Request #5 · ACCESS-NRI/ACCESS-ESM1.6 · GitHub](https://github.com/ACCESS-NRI/ACCESS-ESM1.6/pull/5)

---

<div class="post-metadata">

**Author:** ![harshula](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/harshula/32/256_2.png) [@harshula](https://forum.access-hive.org.au/u/harshula)\
**Post date:** [23 October 2024 22:51 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/25 "2024-10-23T22:51:22Z")

</div>

The latest instructions for running the Pre-release build are here: [Update cable3 by JhanSrbinovsky · Pull Request #5 · ACCESS-NRI/ACCESS-ESM1.6 · GitHub](https://github.com/ACCESS-NRI/ACCESS-ESM1.6/pull/5#issuecomment-2430856965)

---

<div class="post-metadata">

**Author:** ![TommyGatti](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/tommygatti/32/2353_2.png) [@TommyGatti](https://forum.access-hive.org.au/u/TommyGatti)\
**Post date:** [24 October 2024 00:52 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/26 "2024-10-24T00:52:22Z")

</div>

So for future updates to the above prerelease, you would update the UM source code, and then to trigger another prerelease with those changes, you would add another commit to the ACCESS-ESM1.6 PR, since the workflow runs on updates to the pull request. The commit can be:

- Just adding a comment to the `spack.yaml` noting the particular hash of the `HEAD` of the `UM` branch
- Or even an empty commit where the message is why it’s being rebuilt: `git commit --allow-empty -m "Rebuilt to test these new UM changes"`

This all assumes that you’ll be using a branch reference rather than a tag - if you’re using a tag then the workflow would be to just update the `spack.yaml` with the new tag each time!

---

<div class="post-metadata">

**Author:** ![Jhan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/jhan/32/721_2.png) [@Jhan](https://forum.access-hive.org.au/u/Jhan)\
**Post date:** [24 October 2024 00:59 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/27 "2024-10-24T00:59:53Z")

</div>

Great Thanks Tommy. I’ll try it out. IF there is a bug in the UM code modification that stops the compile, where will I find this?

---

<div class="post-metadata">

**Author:** ![Jhan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/jhan/32/721_2.png) [@Jhan](https://forum.access-hive.org.au/u/Jhan)\
**Post date:** [25 October 2024 01:12 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/28 "2024-10-25T01:12:33Z")

</div>

bump

---

<div class="post-metadata">

**Author:** ![Aidan](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/aidan/32/42_2.png) [@Aidan](https://forum.access-hive.org.au/u/Aidan)\
**Post date:** [25 October 2024 05:45 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/29 "2024-10-25T05:45:43Z")

</div>

> [@Jhan](#):
>
> IF there is a bug in the UM code modification that stops the compile, where will I find this?

The workflow will have an error condition, e.g. see this ESM1.5 build:

> <https://github.com/ACCESS-NRI/ACCESS-ESM1.5/pull/14#issuecomment-2420843144>
>
> :rocket: Deploying access-esm1.5 \`2024.05.2\` as prerelease \`pr14-1\`
> 
> \<details\>
> \<…summary\>Details and usage instructions\</summary\>
> 
> This \`access-esm1.5\` model will be deployed as:
> \* \`2024.05.2\` as a Release (when merged).
> \* \`pr14-1\` as a Prerelease (during this PR).
> 
> This Prerelease is accessible on Gadi using:
> \`\`\`bash
> module use /g/data/vk83/prerelease/modules
> module load access-esm1p5/pr14-1
> \`\`\`
> where the binaries shall be on your \`$PATH\`.
> This Prerelease is also accessible on Gadi via \`/g/data/vk83/prerelease/apps/spack/0.22/spack\` in the \`access-esm1p5-\` environment.
> \</details\>
> 
> :hammer\_and\_wrench: Using: spack \`0.22\`, spack-packages \`2024.07.10\`, spack-config \`2024.10.03\`
> \<details\>
> \<summary\>Details\</summary\>
> 
> It will be deployed using:
> \* \`access-nri/spack\` on branch \[\`0.22\`\](https://github.com/ACCESS-NRI/spack/tree/releases/v0.22)
> \* \`access-nri/spack-packages\` version \[\`2024.07.10\`\](https://github.com/ACCESS-NRI/spack-packages/releases/tag/2024.07.10)
> \* \`access-nri/spack-config\` version \[\`2024.10.03\`\](https://github.com/ACCESS-NRI/spack-config/releases/tag/2024.10.03)
> 
> If this is not what was expected, commit changes to \`config/versions.json\`.
> \</details\>

Click on the Red Cross to see the status

 ![Screenshot 2024-10-25 at 4.44.05 pm](https://us1.discourse-cdn.com/flex020/uploads/access1/original/2X/2/2b875339df0e99eddfbf6e79ee611db40a001868.png)

and then click on the “Details” link to see the detail of the output from the commands that failed.

---

<div class="post-metadata">

**Author:** ![harshula](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/harshula/32/256_2.png) [@harshula](https://forum.access-hive.org.au/u/harshula)\
**Post date:** [17 November 2024 23:32 UTC](https://forum.access-hive.org.au/t/building-from-um7-repo/3815/30 "2024-11-17T23:32:10Z")

</div>



[Previous page](https://forum.access-hive.org.au/t/building-from-um7-repo/3815.md?page=1)
