You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: .github/workflows/undeploy-2-start.yml
+2-2
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ jobs:
46
46
if: always()
47
47
run: |
48
48
if [[ "${{ steps.undeploy.outcome }}" == "success" ]]; then
49
-
echo "::notice::Deployment ${{ inputs.env-name }} was successfully removed from ${{ inputs.deployment-environment }}"
49
+
echo "::notice::Deployment ${{ inputs.env-name }} was successfully removed from ${{ inputs.deployment-environment }}, found at ${{ vars.SPACK_LOCATION }}"
50
50
else
51
-
echo "::error::Deployment ${{ inputs.env-name }} couldn't be removed from ${{ inputs.deployment-environment}}. Please check manually."
51
+
echo "::error::Deployment ${{ inputs.env-name }} couldn't be removed from ${{ inputs.deployment-environment}}, found at ${{ vars.SPACK_LOCATION }}. Please check manually."
Copy file name to clipboardexpand all lines: README.md
+42-32
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,35 @@ This workflow obtains the relevant spack and GitHub Environment information, and
33
33
34
34
Using the GitHub Environment, it `ssh`s into the deployment environments `spack` instance, and installs the model associated with the repository that called it. It then copies back relevant metadata and creates a versioned GitHub Release in the caller repository, if it is not a `prerelease` deployment.
35
35
36
+
#### Usage
37
+
38
+
For supported `spack`-installable ACCESS-NRI models, simply call the `deploy-1-setup.yml` reusable workflow from the given repositories workflow file, as shown below. Don't forget to add required inputs!
This will remove every `spack` environment from the deployment target that matches `<model>-*`.
63
+
64
+
38
65
#### Inputs
39
66
40
67
| Name | Type | Description | Required | Default | Example |
@@ -53,13 +80,27 @@ This workflow obtains the relevant spack and GitHub Environment information, and
53
80
54
81
Using the GitHub Environment, it `ssh`s into the deployment environments `spack` instance, and installs the model associated with the repository that called it. It then copies back relevant metadata and creates a versioned GitHub Release in the caller repository, if it is not a `prerelease` deployment.
55
82
83
+
#### Usage
84
+
85
+
For given `spack` environments, we can also remove deployments. For example:
This will remove every `spack` environment from the deployment target that matches `<model>-pre*`.
96
+
56
97
### `validate-json.yml`
57
98
58
99
This workflow is used to validate the `config` folders `*.json` files based on their associated `*.schema.json`. This is used for PR checks on the `build-cd` repo itself.
59
100
60
101
### `create-deployment-spack.yml`
61
102
62
-
This workflow is used to create a version of `spack` on `Gadi`.
103
+
This workflow_dispatch-triggered workflow is used to create a version of `spack` on `Gadi`.
63
104
64
105
#### Inputs
65
106
@@ -69,34 +110,3 @@ This workflow is used to create a version of `spack` on `Gadi`.
69
110
| `spack-packages-version` | string | A version of ACCESS-NRI/spack-packages to be bundled with the install of `spack` | true | `main` | `2023.11.12` |
70
111
| `spack-config-version` | string | A version of ACCESS-NRI/spack-config to be bundled with the install of `spack` | true | `main` | `2024.01.01` |
71
112
| `deployment-location` | true | A path in the deployment environment where Spack should be created. For example, if it is `opt/spack`, spack will be installed under `opt/spack/<spack-version>/` | true | N/A | `/opt/spack` |
72
-
73
-
## Usage
74
-
75
-
### Deployment
76
-
77
-
For supported `spack`-installable ACCESS-NRI models, simply call the `deploy-1-setup.yml` reusable workflow from the given repositories workflow file, as shown below. Don't forget to add required inputs!
0 commit comments