Blocking: Replace Microsoft provided VSCode web build with our own
Description
There are licensing issues with the VSCode web build we get from microsoft. For this and other reasons (i.e. extending vscode behavior), we should:
- Create a fork for VSCode
- Include instructions for updating the fork
- Include CI job for building the assets and including in a GitLab "release"
- Update the
vscode-build
package in this project to point to the GitLab "release" - Let's make sure the fork project lives in somewhere more permanent than the playground.
Notes
Refer to official VS Code build pipelines for reference, e.g.: https://gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork/-/blob/main/build/azure-pipelines/web/product-build-web.yml#L108
Tasks
-
move from sandbox to final project location at: https://gitlab.com/gitlab-org/gitlab-web-ide-vscode-fork -
use appropriate Dockerfile -
Based on the existing vscode pipelines, it looks like we can use the same image they do: vscodehub.azurecr.io/vscode-linux-build-agent:bionic-x64
. Source of this image is here: https://github.com/microsoft/vscode-linux-build-agent/tree/main/bionic-x64
-
-
publish docker image in gitlab-build-images repo: Create Dockerfile.gitlab-vscode-fork-node (gitlab-build-images!570 - merged) -
polish CI config -
make it use the right runner -
tweak to be fast
-
-
set up versioning and tagging -
set up release publishing of versioned artifact
Edited by Paul Slaughter