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
Finally run the console and visit [localhost:9000](http://localhost:9000):
90
96
91
97
```
92
98
./examples/run-bridge.sh
93
99
```
94
100
95
101
#### Enabling Monitoring Locally
102
+
96
103
In order to enable the monitoring UI and see the "Observe" navigation item while running locally, you'll need to run the OpenShift Monitoring dynamic plugin alongside Bridge. To do so, follow these steps:
97
104
98
105
1. Clone the monitoring-plugin repo: https://github.com/openshift/monitoring-plugin
99
106
2.`cd` to the monitoring-plugin root dir
100
107
3. Run
101
-
```
102
-
make install && make start-frontend
103
-
```
108
+
109
+
```
110
+
make install && make start-frontend
111
+
```
112
+
104
113
4. Run Bridge in another terminal following the steps above, but set the following environment variable before starting Bridge:
Note: There could be scenario were you would have to add the new image reference in the "mapping_supplemental_ci_images_ci" file, i.e. to avoid CI downtime for upcoming release cycle.
@@ -135,7 +146,7 @@ To login to the cluster's API server, you can use the following command:
… or, alternatively, use the CRC daemon UI (*Copy OC Login Command --> kubeadmin*) to get the cluster-specific command.
149
+
-… or, alternatively, use the CRC daemon UI (_Copy OC Login Command --> kubeadmin_) to get the cluster-specific command.
139
150
140
151
Finally, prepare the environment, and run the console:
141
152
@@ -213,7 +224,7 @@ yarn run dev
213
224
214
225
If changes aren't detected, you might need to increase `fs.inotify.max_user_watches`. See <https://webpack.js.org/configuration/watch/#not-enough-watchers>. If you need to increase your watchers, it's common to see multiple errors beginning with `Error from chokidar`.
215
226
216
-
Note: ensure `yarn run dev` has finished its initial build before visiting http://localhost:9000, otherwise `./bin/bridge` will stop running.
227
+
-Note: ensure `yarn run dev` has finished its initial build before visiting http://localhost:9000, otherwise `./bin/bridge` will stop running.
217
228
218
229
### Unit Tests
219
230
@@ -265,7 +276,7 @@ yarn run test-cypress-console
265
276
266
277
This will launch the Cypress Test Runner UI in the `console` package, where you can run one or all Cypress tests.
267
278
268
-
**Important:** when testing with authentication, set `BRIDGE_KUBEADMIN_PASSWORD` environment variable in your shell.
279
+
-**Important:** when testing with authentication, set `BRIDGE_KUBEADMIN_PASSWORD` environment variable in your shell.
269
280
270
281
#### Execute Cypress in different packages
271
282
@@ -439,11 +450,13 @@ After building, the server can be run directly with:
Alternatively, you can use the provided Dockerfile.downloads to build an image containing the server. Use the following command to build the Docker image:
Note: If you are running on macOS, you might need to pass the `--platform linux/amd64` flag to the Docker build command. The origin-cli-artifacts image is not supported on macOS.
448
461
449
462
To launch the server using the built image, you can run:
@@ -462,9 +475,10 @@ spamming the telemetry service with repetitive data. Identical violations will n
0 commit comments