Move test symlink to script

This way it works for local testing as well.

I had to use out-build instead of out-vscode-server-min because Jest
throws some obscure error about a handlebars haste map.

Author: code-asher

.github/workflows/ci.yaml

@@ -147,14 +147,7 @@ jobs:
         run: yarn build:vscode
 
       # Our code imports code from VS Code's `out` directory meaning VS Code
-      # must be built before running these tests.  It looks for `out` in order
-      # to work during development but production creates `out-build`,
-      # `out-vscode-server, and `out-vscode-server-min` so symlink to one of
-      # those (during release we move `out-vscode-server-min` to out so using
-      # that gives the closest environment to release).
-      - name: Link VS Code build
-        run: ln -s out-vscode-server-min vendor/modules/code-oss-dev/out
-
+      # must be built before running these tests.
       # TODO: Move to its own step?
       - name: Run code-server unit tests
         run: yarn test:unit

ci/dev/test-unit.sh

@@ -3,12 +3,26 @@ set -euo pipefail
 
 main() {
   cd "$(dirname "$0")/../.."
-  cd test/unit/node/test-plugin
+
+  source ./ci/lib.sh
+
+  pushd test/unit/node/test-plugin
   make -s out/index.js
+  popd
+
+  # Our code imports from `out` in order to work during development but if you
+  # have only built for production you will have not have this directory.  In
+  # that case symlink `out` to a production build directory.
+  local vscode="vendor/modules/code-oss-dev"
+  local link="$vscode/out"
+  local target="out-build"
+  if [[ ! -e $link ]] && [[ -d $vscode/$target ]]; then
+    ln -s "$target" "$link"
+  fi
+
   # We must keep jest in a sub-directory. See ../../test/package.json for more
   # information. We must also run it from the root otherwise coverage will not
   # include our source files.
-  cd "$OLDPWD"
   CS_DISABLE_PLUGINS=true ./test/node_modules/.bin/jest "$@"
 }