alesbrelih / gitlab-ci-ls

46 stars 5 forks source link

Feature request: support remote SSH #138

Open aljaxus opened 1 day ago

aljaxus commented 1 day ago

When using Vscode remote SSH extension, gitlab-ci-ls extension fails with the following error code;

[Error - 1:32:38 PM] Gitlab LS client: couldn't create connection to server.
Launching server using command gitlab-ci-ls failed. Error: spawn gitlab-ci-ls ENOENT

System info (vscode Help > About)

Version: 1.93.1
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Linux x64 6.10.10-arch1-1

Extension is installed on the client side and host (remote) side.

alesbrelih commented 1 day ago

Hey,

I've tested remote SSH feature and got the same error. First of all you need to install the gitlab-ci-ls manually on the SSH host, installing extension isn't enough (using cargo or just using the released binary). I've tested both ways and got positive results:

  1. I've installed rustup and some dependencies and ran cargo install gitlab-ci-ls to install the binary. Then I've updated remote settings for the extension like: Screenshot 2024-10-01 at 20 55 13

I've also had to set up cache/log folders accordingly to my remote setting. (Ignore the /root/... was too lazy to create an actual user environment.

And then it started working.

  1. I've just used the latest release

wget https://github.com/alesbrelih/gitlab-ci-ls/releases/download/0.21.4/gitlab-ci-ls-x86_64-unknown-linux-gnu -O /usr/local/bin/gitlab-ci-ls && chmod +x /usr/local/bin/gitlab-ci-ls

And updated settings accordingly because now it was in my path already. Even though I could add the .cargo/bin to my path but as I said I'm lazy 😅

Settings:

Screenshot 2024-10-01 at 20 58 58

I've also restarted VScode whenever I did any changes. Not sure how it propagates them.

Hope this helps. If it still won't be working let me know.