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: docs/OCP_CI_Tutorials/Triggering/Triggering_Guide.md
+13-3
Original file line number
Diff line number
Diff line change
@@ -135,6 +135,7 @@ In practice, the application currently served in the Openshift-Ci env is configu
135
135
Since the tool is based on the Flask framework, it is natural to deploy a Lightsail container and the configuration is quite easy, with respect to the tool's current configuration options.
136
136
137
137
Step by step deployment:
138
+
138
139
1. Sign in to your AWS account, go to the Lightsail control panel, and then go to `Containers`
139
140
2. Press `create container service` on the top right button
140
141
3. Inside the `Create Container Service` page, make sure the available region is automatically selected (usually the region closest to the user)
@@ -143,21 +144,27 @@ Step by step deployment:
143
144
6. Press `Create container service`. It will probably take a few minutes.
144
145
7. Once you can see the onboarded container in the Lightsail containers dashboard, go to it's `Deployments` section
145
146
8. Create a new deployment with the following configuration:
147
+
146
148
```commandline
147
149
Container name: ci-jobs-trigger
148
150
Image: quay.io/redhat_msi/ci-jobs-trigger
149
151
```
152
+
150
153
Add the following environment variables:
151
-
```
154
+
155
+
```commandline
152
156
[Key]:[Value]
153
157
FLASK_DEBUG: 1
154
158
CI_JOBS_TRIGGER_LISTEN_IP: 0.0.0.0
155
159
```
160
+
156
161
Open ports:
157
-
```
162
+
163
+
```commandline
158
164
[Port]:[Protocol]
159
165
5000: HTTP
160
166
```
167
+
161
168
9. Add a public endpoint corresponded to the container name, and change the Health check path to: `/healthcheck`
162
169
10. Hit `Save and deploy` and once the deployment is active, you're set to go!
163
170
@@ -167,8 +174,11 @@ See a doc about deploy [Flask apps on AWS Lightsail](https://aws.amazon.com/tuto
167
174
### Verify the running app
168
175
169
176
For verify the app is working, make sure you:
177
+
170
178
- Set the server url path in Vault to the containers domain, should be something similar to:
- Manually trigger the job `periodic-ci-rhpit-interop-tests-main-retrigger-poc-failure-test` using the gangway api. The job will send a Slack verification of the working app.
0 commit comments