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: apps/koku-ui-hccm/RELEASE.md
+56-7Lines changed: 56 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,32 +2,81 @@
2
2
3
3
This doc describes how to release Koku UI to each staging environment. Note that this should be done in order for testing purposes.
4
4
5
-
## Release script
5
+
## Release branches
6
6
7
-
The release script creates a PR with a unique SHA, used for a namespace \`ref\` in the app-interface repo. The script also ensures that code is always pulled from the correct branches. For example, we always:
7
+
The release script creates a koku-ui PR with a unique SHA, used for a namespace \`ref\` in app-interface. The script also ensures that code is always pulled from the correct branches. For example, we always:
8
8
9
-
1. Pull from master when pushing to prod-hccm
9
+
1. Pull from master when pushing to stage-hccm
10
+
2. Pull from stage-hccm when pushing to prod-hccm
10
11
11
12
Note: Pushing to master automatically deploys to the stage.
12
13
13
14
Please allow the PR to build successfully and merge before running the script again.
14
15
16
+
### Release to stage-hccm
17
+
18
+
```
19
+
sh ../../scripts/release-branch.sh -s
20
+
```
21
+
15
22
### Release to prod-hccm
16
23
17
24
```
18
-
sh scripts/release-branch.sh -p
25
+
sh ../../scripts/release-branch.sh -p
19
26
```
20
27
21
-
## Deployment
28
+
### Wrapper for all release and deployment functionality
29
+
30
+
```
31
+
node ../../scripts/release-all.js
32
+
```
22
33
23
-
After all PRs have been merged, update the \`koku-ui-hccm\` resource in https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/hccm/deploy-clowder.yml
34
+
Follow the prompts below.
35
+
36
+
* Which app do you want to release? `koku-ui-hccm`
37
+
* Which Chrome environment you want to release? `stage`
38
+
* Do you want to release to app-interface? `N`
39
+
40
+
## Deployments for app-interface
41
+
42
+
The release script will update app-interface with the latest SHA refs from the koku-ui branches above. The script also ensures that SHA refs are always pulled from the correct branches. For example, we always:
43
+
44
+
1. Pull from stage-hccm when updating the stage deployment in app-interface
45
+
2. Pull from prod-hccm when updating the prod deployment in app-interface
46
+
47
+
### Release to app-interface
48
+
49
+
```
50
+
sh ../../scripts/release-app-interface.sh -<p|s>
51
+
```
52
+
53
+
### Wrapper for all release and deployment functionality
54
+
55
+
```
56
+
node ../../scripts/release-all.js
57
+
```
58
+
59
+
Follow the prompts below.
60
+
61
+
* Which app do you want to release? `koku-ui-hccm`
62
+
* Which Chrome environment you want to release? `stage`
63
+
* Do you want to release to app-interface? `Y`
64
+
65
+
### Manual deployment
66
+
67
+
After all koku-ui PRs have been merged, update the \`koku-ui-hccm\` resource in https://gitlab.cee.redhat.com/service/app-interface/-/blob/master/data/services/insights/hccm/deploy-clowder.yml
24
68
25
69
Use the latest commit of each branch to update namespaces \`ref\` in the app-interface repo. Don't use a merge commit, SHAs must be unique when images are created for each branch.
0 commit comments