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
{{ message }}
This repository has been archived by the owner on Jul 10, 2024. It is now read-only.
i've noticed that the Appium Dashboard remains empty when I run sessions with a hub + node configuration of device farm.
Currently im running device farm with one hub and 8 nodes in a Kubernetes cluster.
It uses ConfigMap to dynamicly apply the hub/node config. This is for the hub:
This works just fine. I also configured that the service is reachable via port 31337 not 4723, so I can lookup -->
"my.domain.com:31337/device-farm/" and "my.domain.com:31337/dashboard/".
Im using:
Appium beta.64
Appium Dashboard 2.02
Device-Farm 7.2
The 8 nodes all have an Android Emulator with API23 (so fairly old) and Espresso 2.15.0
Does Dashboard even work in this kind of setup? Has it been tested for remote execution?
I can provide additional logs if necessary.
The text was updated successfully, but these errors were encountered:
Currently appium-dashboard plugin won't work well with Hub + Node setup. The logs and videos can only be saved in node level and in the hub you wont see any session details.
@win5923 create a Dockerfile with Appium and its Dependencies and deploy the image on a pod. Copy and paste a start server script with needed parameters (like plugins, relaxed security etc.) or create a yaml/json config and pass it into your start server command.
Im running a pod with only Appium and device-farm plugin that serves as a hub and a handful of pods running Appium + device-farm + espresso driver with emulators as node.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
i've noticed that the Appium Dashboard remains empty when I run sessions with a hub + node configuration of device farm.
Currently im running device farm with one hub and 8 nodes in a Kubernetes cluster.
It uses ConfigMap to dynamicly apply the hub/node config. This is for the hub:
and this is for the node:
This works just fine. I also configured that the service is reachable via port 31337 not 4723, so I can lookup -->
"my.domain.com:31337/device-farm/" and "my.domain.com:31337/dashboard/".
Im using:
Appium beta.64
Appium Dashboard 2.02
Device-Farm 7.2
The 8 nodes all have an Android Emulator with API23 (so fairly old) and Espresso 2.15.0
Does Dashboard even work in this kind of setup? Has it been tested for remote execution?
I can provide additional logs if necessary.
The text was updated successfully, but these errors were encountered: