@@ -138,20 +138,22 @@ jobs:
138
138
path : |
139
139
vendor/modules/code-oss-dev/.build
140
140
vendor/modules/code-oss-dev/out-build
141
- vendor/modules/code-oss-dev/out-vscode
142
- vendor/modules/code-oss-dev/out-vscode-min
143
- key : vscode-build-${{ steps.vscode-rev.outputs.rev }}
141
+ vendor/modules/code-oss-dev/out-vscode-server
142
+ vendor/modules/code-oss-dev/out-vscode-server- min
143
+ key : vscode-server- build-${{ steps.vscode-rev.outputs.rev }}
144
144
145
145
- name : Build vscode
146
146
if : steps.cache-vscode.outputs.cache-hit != 'true'
147
147
run : yarn build:vscode
148
148
149
- # Our code imports code from VS Code's output directory meaning VS Code
149
+ # Our code imports code from VS Code's `out` directory meaning VS Code
150
150
# must be built before running these tests. It looks for `out` in order
151
- # to works during development (for release we move `out-build` to `out`)
152
- # so symlink `out` to `out-build` as this is a production build.
153
- - name : Link vscode
154
- run : ln -s out-build vendor/modules/code-oss-dev/out
151
+ # to work during development but production creates `out-build`,
152
+ # `out-vscode-server, and `out-vscode-server-min` so symlink to one of
153
+ # those (during release we move `out-vscode-server-min` to out so using
154
+ # that gives the closest environment to release).
155
+ - name : Link VS Code build
156
+ run : ln -s out-vscode-server-min vendor/modules/code-oss-dev/out
155
157
156
158
# TODO: Move to its own step?
157
159
- name : Run code-server unit tests
0 commit comments