Testing a dependency within CI

[rchl]

Testing a dependency within CI

[rchl]

For context, when doing the same in a local, clean ST build, I'm getting the same message and what I need to do to get that dependency registered in the loader is I have to manually trigger Package Control: Install Local Dependency from the Command Palette and select lsp_utils.

So I'm trying to figure out if there is some solution to that without involving any changes in PC itself since that would take a very long time, even if accepted.

[rchl]

One, not that clean, solution that just came to my mind is:

• run github.sh install_package LSP-pyright master https://github.com/sublimelsp/LSP-pyright.git to install a package that requires lsp_utils
• run github.sh install_package_control to let PC install the lsp_utils dependency
• in the next CI step, manually delete the installed dependency and then add my local version

[randy3k]

One solution is to remove the .git subdirectory of the repo. I remember I have to do it for one particular instance.

[rchl]

If I do that then PC will overwrite the dependency directory with the latest released version instead of the one I want to test.

[rchl]

My idea above seems to have worked (see sublimelsp/lsp_utils@759e975).

Obviously it's very hacky though and I would want to avoid referencing the Packages path in the CI workflow and rely completely on the original script...

[randy3k]

I thing we could add a flag to the bootstrap command so that the current repo is not copied to ST https://github.com/SublimeText/UnitTesting/blob/master/sbin/ci.sh#L29
And extract this part as a separate function which could then be called later to replace the installed dependency.

[rchl]

Yeah, that should work. Was hoping we could find some alternative angle at this issue that I couldn't think of. :)