-
Task
-
Resolution: Done
-
Major
-
3.7.0.GA
-
False
-
None
-
False
-
-
There are a lot of vsix plugins used by pluginregistry, building them as part of the cachito migration in CRW-3336 will increase the build time by a lot so we're going to create a separate build for it.
process will most likely be:
- jenkins job orchestrator, loosely based on dsc_3.x or get-3rd-party-sources job (which can push files to download.devel)
- variation on https://github.com/redhat-developer/devspaces-vscode-extensions/blob/main/.ci/extension_build_publish.sh
Some older extensions in https://github.com/redhat-developer/devspaces-vscode-extensions appear to have exceptional Dockerfiles suggesting other appraoches / environments needed to build these vsix files:
- https://github.com/redhat-developer/devspaces-vscode-extensions/blob/main/shellcheck/Dockerfile#L24 (yarn, gulp, etc.)
We can put files in /mnt/rcm-guest/staging/devspaces/build-requirements on download.devel using similar code from as dsc_3.x or get-3rd-party-sources, subject to change as per the directions in CRW-3598 (using rsync only)
Then these vsix files can be retrieved at build-time using something like https://pkgs.devel.redhat.com/cgit/containers/devspaces-code/tree/fetch-artifacts-url.yaml?h=private-nboldt-CRW-3160-cachito-code-no-symlink
- is depended on by
-
CRW-4116 versions of plugins in the plugin registry should be hardcoded to supported/tested versions
- Resolved
- is related to
-
CRW-4165 Verify vsix package.json and other metadata are compatible with the current version of vscode being targetted
- Resolved
-
CRW-4115 Unit / Integration test for plugin registry: can all the included plugins be installed
- Closed
-
CRW-4325 Update Vscode-Jupyter plugin to build via dockerfile
- Closed
- relates to
-
CRW-4128 When pushing sources and dsc tarballs, use a unique CR folder each time
- Closed
-
CRW-4136 Use xdebug.php-debug VSCode extension instead of felixfbecker.php-debug
- Closed
- links to
- mentioned on