Local Source, Remote Build

[pepi55]

I would like support for local source and remote build.
Something like this:

|-------------|           |--------------------|
|  Local OS   |           |     Remote OS      |
||-----------||           ||------------------||
||  VS Code  ||           ||  VS Code Server  ||
||-----------|| (RSYNC?)  || Build/Debug etc. ||
| Source Code-|---------->||------------------||
|-------------|           |--------------------|

My use case is that I use build hosts which are not permanent. They get destroyed + rebuilt every x amount of time. This means that any changes that are made and not committed in git are lost. Sometimes big changes have to be started all over again.

It would be very useful if VSCode had support for such scenarios, if not vscode-remote support, then something in tasks.json similar to remoteMachineName & co. so I can create a task to rsync to a remote machine and run tasks on the build host from a local VSCode workspace without having to manually ssh into the remote and manually execute all steps.

I think that if vscode-remote is part of VSCode, then this should also be part of it because having source code locally and building on a remote server or having source code on a remote server and building there as well, should really be an option the developer could configure.

If there is such a feature already, I haven't been able to find it. Also, keep in mind that having an extension/task that rsyncs back from the remote defeats the purpose because that means that the source has to be on the machine already, in which case I might as well use the vscode-remote extension. This is also error-prone as it is one "I forgot to rsync back to the host" away from losing a lot of uncommitted progress. I also develop on a Windows dev machine without the possibility of installing new applications, which means I can't rsync from the build host to the dev machine. Lastly, I prefer to keep VSCode as lean as possible since I change machines frequently and have to remember all extensions I use for a new install.

Thanks for understanding, I hope you can also see why this feature would be useful and will consider adding it to VSCode.

[bilderbuchi]

Enabling this in an automated fashion could be a viable workaround around the upstream WSL filesystem performance issues microsoft/WSL#4197 microsoft/WSL#873!

[vscodenpa]

This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!

[bilderbuchi]

Should a bot that rejects-closes issues not use the "close as not planned" action, rather than "close as completed"? This issue is not completed, after all?