This message was deleted.
# community-support
s
This message was deleted.
s
m
I was under the impression that the debugger port is different than the daemon port
s
oh right, my mistake
m
no worries, I had came across the same thing too yesterday when searching 😆
🤣 1
and setting
0
will pick a random available port
that code above is entered from here, https://github.com/gradle/gradle/blob/0bd581a28013a7df9a9f7f8fe8230638aad812b1/sub[…]org/gradle/launcher/daemon/server/DaemonTcpServerConnector.java
Copy code
/**
 * Opens a TCP connection for clients to connect to communicate with a daemon.
 */
oddly, I can't find any documentation or tutorials online of people setting up the IntelliJ Gradle Plugin to work over SSH. There is only a brief mention of it on this page: https://www.jetbrains.com/help/idea/run-targets.html#supported-rcs
s
that does surprise me. perhaps try extending the issue to android studio? it may have similar overlap on the issue
i feel like most people build locally then remotely debug, not both of those things
m
yea, that's a good point
I did see more discussion online when it came to using the gradle debugger remotely -- barely anything for building remotely