diff --git a/docs/admins/ci-cd-workflow.svg b/docs/admins/ci-cd-workflow.svg new file mode 100644 index 000000000..25eb04206 --- /dev/null +++ b/docs/admins/ci-cd-workflow.svg @@ -0,0 +1 @@ + diff --git a/docs/admins/cicd-github-actions.qmd b/docs/admins/cicd-github-actions.qmd index 7f29b1868..8491cb936 100644 --- a/docs/admins/cicd-github-actions.qmd +++ b/docs/admins/cicd-github-actions.qmd @@ -13,10 +13,10 @@ These workflows are stored in the DataHub repo in the The basic order of operations is as follows: -1. PR is created in the datahub repo. +1. A pull request is created in the datahub repo. 1. The labeler workflow applies labels based on the [file type and/or location](https://github.com/berkeley-dsep-infra/datahub/blob/staging/.github/labeler.yml). -1. On PR merge to staging, if the labels match any hub, support or node placeholder deployments those specific systems are deployed. -1. On PR merge to prod, only hubs are deployed (again based on labels). +1. When the pull request is merged to `staging`, if the labels match any hub, support or node placeholder deployments those specific systems are deployed. +1. When the pull request is merged to prod, only the hubs that have been modified are deployed (again based on labels). The hubs are deployed via [hubploy](https://github.com/berkeley-dsep-infra/hubploy), which is our custom wrapper for `gcloud`, `sops` and `helm`. @@ -117,6 +117,8 @@ a list of what's to be deployed. That list is iterated over, and [hubploy](https://github.com/berkeley-dsep-infra/hubploy) is used to deploy only the flagged hubs. +![CI/CD workflow for single-user server images](ci-cd-workflow.svg) + #### Support and node-placeholder charts Each of these deployments has their own workflow, which only runs on pushes to