Skip to content

Build and deployment documentation#280

Merged
ccarouge merged 17 commits intomainfrom
279-build-and-deployment-documentation
Mar 5, 2026
Merged

Build and deployment documentation#280
ccarouge merged 17 commits intomainfrom
279-build-and-deployment-documentation

Conversation

@ccarouge
Copy link
Copy Markdown
Member

1. Summary:

Added documentation about the building and deployment process for ACCESS-ESM1.6

2. Issues Addressed:

3. Dependencies (e.g. on payu, or model)

This change requires changes to (note pull request(s) where relevant):

  • workflow manager (payu):
  • model deployment (ACCESS-ESM1.6):
  • model component or library dependency:
  • input workflow:

4. Ad-hoc Testing

What ad-hoc testing was done? How are you convinced this change is correct (plots are good)?

Documentation only. No testing done. Relying on build preview in PR to correct formatting.

5. CI Testing

  • !test repro has been run
  • N/A: documentation only

6. Reproducibility

Is this reproducible with the previous commit? (If not, why not?)

  • Yes
  • No - !test repro commit has been run.

8. Manifests

Have you changed the executable, the input files and/or the restart files?

  • Yes
  • No

If yes, have you updated the manifests?

  • Yes
  • No

To update the manifests, run payu setup (in a cloned copy of your feature branch) with reproducibility tests turned off:

manifest:
  reproduce:
    exe: false
    input: false
    restart: false
runlog:
  enable: false

Then commit the newly created manifest files (under manifests/) only to the branch for this PR.

7. Documentation

Is the documentation updated?

  • Yes
  • N/A

9. Merge Strategy

  • Merge commit
  • Rebase and merge
  • Squash

@ccarouge ccarouge linked an issue Nov 21, 2025 that may be closed by this pull request
@ccarouge
Copy link
Copy Markdown
Member Author

@atteggiani The config docs for ESM1.6 fail to deploy with the preview. Does it need all the PR previews to work in order to deploy? I'm happy to go and fix PR 252, just making sure that should solve the problem before investing time.

@atteggiani
Copy link
Copy Markdown
Collaborator

atteggiani commented Nov 21, 2025

@atteggiani The config docs for ESM1.6 fail to deploy with the preview. Does it need all the PR previews to work in order to deploy? I'm happy to go and fix PR 252, just making sure that should solve the problem before investing time.

Yes it needs all PR previews to work, unfortunately.
If the fix takes time, you might try writing a line with !no-pr-preview in the body of the PR (PR #252 in this case). It should not trigger that PR preview. I haven't tested this properly due to RTD changes so it might not work, but it's worth a try.
It needs to be the first line of the PR body.

Then you would need to re-trigger this PR. You cannot simply retrigger the build manually, so you'll have to add a new commit or amend (no edits) and force push the latest one.

@chrisb13
Copy link
Copy Markdown
Contributor

@ccarouge
Copy link
Copy Markdown
Member Author

PR #252 was fixed and the preview workflow ran from #252 has now created a preview (dismiss the failed build in this PR).

@chrisb13 I'll have a look at the links you shared.

@chrisb13
Copy link
Copy Markdown
Contributor

@chrisb13 I'll have a look at the links you shared.

Sure thing, @anton-seaice might be a helpful person to canvas too.

Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
Comment thread documentation/docs/pages/infrastructure/building.md
aidanheerdegen
aidanheerdegen previously approved these changes Jan 19, 2026
Copy link
Copy Markdown
Member

@aidanheerdegen aidanheerdegen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of comments, but otherwise seems good, thanks.

Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
@ccarouge
Copy link
Copy Markdown
Member Author

@anton-seaice Could you review this, please? I will be away so if you can review for 2nd Feb that would be great.

Copy link
Copy Markdown
Collaborator

@anton-seaice anton-seaice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry a bit of a chaotic review, I can have another look as needed

Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
Comment thread documentation/docs/pages/infrastructure/building.md
Comment thread documentation/mkdocs.yml
Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
@ccarouge
Copy link
Copy Markdown
Member Author

Thanks for the review @anton-seaice . I've replied to a few comments and I have a modified version of the text for review.

Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Comment thread documentation/docs/pages/infrastructure/Building.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Comment thread documentation/docs/pages/infrastructure/Deployment.md Outdated
Copy link
Copy Markdown
Collaborator

@anton-seaice anton-seaice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks - good . Some minor refinements from me

@ccarouge
Copy link
Copy Markdown
Member Author

ccarouge commented Mar 2, 2026

@anton-seaice I've updated these build instructions for ESM1.6. Do you mind if I rebase so I can sign commits that aren't signed? It will break the review stuff so I prefer to ask before going ahead.

Another question: do we want to wait for the release of ESM1.6 to push this live or does it not matter? A few things here will only be accessible or possible for users after a release.

@anton-seaice
Copy link
Copy Markdown
Collaborator

No concerns about either.

I think we wont advertise the docs until we advertise the release, so its fine to update the docs

@ccarouge ccarouge force-pushed the 279-build-and-deployment-documentation branch from 1e477c3 to 224df5a Compare March 4, 2026 04:38
@ccarouge
Copy link
Copy Markdown
Member Author

ccarouge commented Mar 4, 2026

@anton-seaice One last one! I've rebased the changes to sign off everything, I've checked all the links and re-read the pages after the rebase to check the text looked correct.

@ccarouge ccarouge requested a review from anton-seaice March 4, 2026 05:18
Copy link
Copy Markdown
Collaborator

@anton-seaice anton-seaice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks Claire !

@ccarouge ccarouge merged commit 9fcc4c0 into main Mar 5, 2026
22 checks passed
@anton-seaice anton-seaice deleted the 279-build-and-deployment-documentation branch March 24, 2026 04:22
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.

Build and deployment documentation

5 participants