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
| SYNAPSE_PASSWORD | Synapse service user token (PAT) | glY4283tLQHZ...0eXAiOi...JKV1QiL |
44
42
45
43
Context specific secrets for each environment that corresponds to a git branch (develop/staging/prod):
46
44
@@ -57,8 +55,9 @@ Context specific secrets for each environment that corresponds to a git branch (
57
55
## Self hosted runners
58
56
59
57
[agora2-infra] repository deploys a bastian host in AWS for each environment which have access to
60
-
the databases. We manually configure a [Github self-hosted runner] for each bastian host,
61
-
a label is applied to each runner to match the corresponding deployment branch name (develop/staging/prod).
58
+
the databases. We manually configure a [Github self-hosted runner](https://docs.github.com/en/actions/hosting-your-own-runners)
59
+
for each bastian host, a label is applied to each runner to match the corresponding git branch name (develop/staging/prod).
60
+
62
61
Each runner corresponds to an environment which corresponds to a git branch. The update is
63
62
executed from these runners. When a push happens on a branch (i.e. develop), the update
64
63
is executed on the `agora-bastian-develop` runner which in turn updates the development database.
@@ -67,6 +66,58 @@ is executed on the `agora-bastian-develop` runner which in turn updates the deve
67
66
![alt text][self_hosted_runners]
68
67
69
68
69
+
### Setup self hosted runners
70
+
71
+
Github self hosted runners are deployed with a [Sceptre template config file])(https://github.com/Sage-Bionetworks/agora2-infra/blob/main/config/agoradev/develop/agora-bastian.yaml).
72
+
73
+
Self Hosted Runner setup:
74
+
* Deploy the template to the Agora AWS account.
75
+
* Login to AWS console and goto `EC2 -> select the deployed instance -> Connect -> Session Manager -> Connect` to gain ssh access to the instance.
76
+
* Follow the instructions to install the [Github self hosted runner](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository). We installed it to the `/home/ssm-user/actions-runner` folder.
77
+
* Run the `config.sh` script to configure the runner. !! Important !! Make sure to set the runner `name` and `label` corresponding to the desired deployment environment (develop/staging/prod)..
Enter the name of the runner group to add this runner to: [press Enter for Default]
103
+
104
+
Enter the name of runner: [press Enter for ip-10-XXX-XXX-XXX] agora-bastian-prod
105
+
106
+
This runner will have the following labels: 'self-hosted', 'Linux', 'X64'
107
+
Enter any additional labels (ex. label-1,label-2): [press Enter to skip] prod
108
+
109
+
√ Runner successfully added
110
+
√ Runner connection is good
111
+
112
+
# Runner settings
113
+
114
+
Enter name of work folder: [press Enter for _work]
115
+
116
+
√ Settings Saved.
117
+
```
118
+
* Setup the [GH runner agent to run as a service](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service)
119
+
* Run the agent and then check the [GH Runners page](https://github.com/Sage-Bionetworks/agora-data-manager/settings/actions/runners) to make sure that the runner is in `Idle` status.
0 commit comments