Skip to content

Commit 46c1578

Browse files
committed
Adding more clarity to the steps. First step should be last step.
1 parent f60435b commit 46c1578

File tree

1 file changed

+9
-11
lines changed

1 file changed

+9
-11
lines changed
Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,15 @@
1-
# Operations: The `chime-live` Cluster
1+
# Operations: Prepare New Chime Release
22

33
At the end of following this process you will have deployed a new CHIME version to https://penn-chime.phl.io
44

55
## Start Here
66

7-
## Deploying a New CHIME Version
7+
## Prepare Chime on the Develop Branch
88

9-
1. [Create a new release](release-process.md)
10-
2. Wait for the `Docker` GitHub Actions workflow to complete
11-
3. Verify the new version shows up at the top as "Latest version" here: https://github.com/CodeForPhilly/chime/packages/155340
12-
4. Open a new issue on GitHub titled "Deploy chime $VERSION" (ex: https://github.com/CodeForPhilly/chime/issues/98)
9+
1. Open a new issue on GitHub titled "Deploy chime $VERSION" (ex: https://github.com/CodeForPhilly/chime/issues/98)
1310
* Note the PR in which the release was approved
1411
* Confirm that the tag for the version was created
15-
5. Create a local branch (based on "develop") to perform deploy time changed on, named "deploy/$VERSION"
12+
2. Create a local branch (based on "develop") to perform deploy time changed on, named "deploy/$VERSION"
1613

1714
```bash
1815
export VERSION=x.x.x #set this to the release version you are releasing. (export VERSION=1.1.1 for version 1.1.1)
@@ -21,22 +18,23 @@ At the end of following this process you will have deployed a new CHIME version
2118
git checkout -b deploy/$VERSION # this will ultimately create a branch deploy/1.1.1 (from the reference above)
2219
```
2320

24-
6. Update the app.yaml manifest file using an editor. You will need to change the line that has: ```- image: docker.pkg.github.com/codeforphilly/chime/penn-chime:<insert versions here>```
21+
3. Update the app.yaml manifest file using an editor. You will need to change the line that has: ```- image: docker.pkg.github.com/codeforphilly/chime/penn-chime:<insert versions here>```
22+
* After that is complete, update your branch.
2523

2624
```bash
2725
git add k8s/app.yml
2826
git diff --staged
2927
git commit -m "Deploy chime $VERSION"
3028
```
3129

32-
7. Push changes
30+
4. Push changes
3331

3432
```bash
3533
git push -u origin deploy/$VERSION
3634
```
3735

38-
8. [Open PR on GitHub](https://github.com/CodeForPhilly/chime/compare) to merge changes back into develop, ideally with
36+
5. [Open PR on GitHub](https://github.com/CodeForPhilly/chime/compare) to merge changes back into develop, ideally with
3937
the review of another DevOps admin whenever possible. Ensure to link
4038
to the PR in the deployment issue previously opened on GitHub.
4139

42-
9. One approved you will need to [create a release to auto deploy](release-process.md)
40+
6. One approved you will need to [create a release to auto deploy](release-process.md)

0 commit comments

Comments
 (0)