Use CI build targets

The target we have been using has started throwing all sorts of errors
during the build (even without any of our patches).  After checking the
VS Code repo I think these are the ones we should actually be using.
They are way faster, too.

Author: code-asher

ci/build/build-release.sh

@@ -6,10 +6,6 @@ set -euo pipefail
 # product.json, and add shrinkwraps.  This results in a generic NPM package that
 # we published to NPM and also use to compile platform-specific packages.
 
-# MINIFY controls whether minified VS Code is bundled. It must match the value
-# used when VS Code was built.
-MINIFY="${MINIFY-true}"
-
 # node_modules are not copied by default.  Set KEEP_MODULES=1 to copy them.
 KEEP_MODULES="${KEEP_MODULES-0}"
 

ci/build/build-vscode.sh

@@ -3,9 +3,6 @@ set -euo pipefail
 
 # Builds vscode into lib/vscode/out-vscode.
 
-# MINIFY controls whether a minified version of vscode is built.
-MINIFY=${MINIFY-true}
-
 delete-bin-script() {
   rm -f "lib/vscode-reh-web-linux-x64/bin/$1"
 }
@@ -112,9 +109,8 @@ EOF
   # this because we have an NPM package that could be installed on any platform.
   # The correct platform dependencies and scripts will be installed as part of
   # the post-install during `npm install` or when building a standalone release.
-  node --max-old-space-size=16384 --optimize-for-size \
-       ./node_modules/gulp/bin/gulp.js \
-       "vscode-reh-web-linux-x64${MINIFY:+-min}"
+  npm run gulp core-ci
+  npm run gulp vscode-reh-web-linux-x64-min-ci
 
   # Reset so if you develop after building you will not be stuck with the wrong
   # commit (the dev client will use `oss-dev` but the dev server will still use

patches/fix-build.diff

@@ -22,4 +22,3 @@ clipboard.diff
 display-language.diff
 trusted-domains.diff
 signature-verification.diff
-fix-build.diff