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
| SE_RECORD_AUDIO | false | Flag to enable recording the audio source (default is Pulse Audio input) ||
123
123
| SE_AUDIO_SOURCE | -f pulse -ac 2 -i default | FFmpeg arguments to record the audio source ||
124
+
| SE_BROWSER_BINARY_LOCATION ||||
125
+
| SE_NODE_BROWSER_NAME ||||
126
+
| SE_NODE_CONTAINER_NAME ||||
127
+
| SE_NODE_HOST ||||
128
+
| SE_NODE_MAX_CONCURRENCY || When node is handled both browser and relay, SE_NODE_MAX_CONCURRENCY is used to configure max concurrency based on sum of them ||
129
+
| SE_NODE_RELAY_BROWSER_NAME ||||
130
+
| SE_NODE_RELAY_MAX_SESSIONS ||||
131
+
| SE_NODE_RELAY_PLATFORM_NAME ||||
132
+
| SE_NODE_RELAY_PLATFORM_VERSION ||||
133
+
| SE_NODE_RELAY_PROTOCOL_VERSION ||||
134
+
| SE_NODE_RELAY_STATUS_ENDPOINT ||||
135
+
| SE_NODE_RELAY_URL ||||
136
+
| SE_NODE_STEREOTYPE || Capabilities in JSON string to overwrite the default Node stereotype ||
137
+
| SE_NODE_STEREOTYPE_EXTRA || Extra capabilities in JSON string that wants to merge to the default Node stereotype ||
In another case, if you want to retain the default Node stereotype and append additional capabilities, you can use the `SE_NODE_STEREOTYPE_EXTRA` environment variable to set your capabilities. Those will be merged to the default stereotype. For example:
This help setting custom capabilities for matching specific Nodes. For example, you added your custom capabilities when starting the Node, and you want assign a test to run on that Node which matches your capabilities. For example in test code:
Noted: Your custom capabilities with key values should be in W3C capabilities convention, extension capabilities key must contain a ":" (colon) character, denoting an implementation specific namespace.
1140
+
1141
+
Noted: Ensure that Node config `detect-drivers = false` in `config.toml` (or `--detect-drivers false` in CLI option) to make feature setting custom capabilities for matching specific Nodes get working.
1142
+
1143
+
In addition, default Node stereotype includes capability `se:containerName` which can visible in node capabilities, or session capabilities to identify the container name where the node/session is running. **The prefixed `se:containerName` is not included in slot matcher**. By default, value is getting from `hostname` command in container, this value is equivalent to the `container_id` that you saw via `docker ps` command. If you want to override this value, you can set the environment variable `SE_NODE_CONTAINER_NAME` to your desired value. For example, when deploy to Kubernetes cluster, you can assign Pod name to env var `SE_NODE_CONTAINER_NAME` to track a node is running in which Pod.
1144
+
1145
+
```yaml
1146
+
env:
1147
+
- name: SE_NODE_CONTAINER_NAME
1148
+
valueFrom:
1149
+
fieldRef:
1150
+
fieldPath: metadata.name
1151
+
```
1152
+
1153
+
In an advanced case, where you control to spawn up a Node container, let it register to Hub, and then trigger a test to be assigned exactly to run on that Node. By default, the value of command `$(hostname)` is added to capability name `container:hostname` in Node stereotype. Combine with above feature setting custom capabilities for matching specific Nodes. You can use the `hostname` of the Node container just spawned up and set it as a custom capability. For example, in Python binding:
0 commit comments