Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup a CI to build 3rd party vscode extensions #14677

Closed
l0rd opened this issue Sep 26, 2019 · 5 comments
Closed

Setup a CI to build 3rd party vscode extensions #14677

l0rd opened this issue Sep 26, 2019 · 5 comments
Assignees
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@l0rd
Copy link
Contributor

l0rd commented Sep 26, 2019

Is your enhancement related to a problem? Please describe.

Those extensions are only available on the marketplace but we cannot download the vs code extensions directly from the marketplace (#14573)

Describe the solution you'd like

Setup a build to generate the vsix files and publish them on https://download.jboss.org/jbosstools/vscode/3rdparty/ to make them available for any Che workspace.

@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system. team/productization labels Sep 26, 2019
@l0rd l0rd added this to the 7.3.0 milestone Sep 26, 2019
@benoitf
Copy link
Contributor

benoitf commented Sep 26, 2019

related to Theia as well: eclipse-theia/theia#6183

BTW there is not only these 2 extensions AFAIK. We should provide all vscode builtin extensions. (https://github.com/microsoft/vscode/tree/master/extensions)

@nickboldt
Copy link
Contributor

@benoitf are you saying we should be building everything from source? If so, ok, yes, that's ultimately better for product support, but ouch, that's a lot of work ;)

@mkuznyetsov this one's for you. could be implemented via Jenkinsfile in a subfolder of https://github.com/redhat-developer/codeready-workspaces/tree/master/dependencies/che-plugin-registry and built in a job in https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Builds/

@nickboldt
Copy link
Contributor

WIP in https://issues.jboss.org/browse/CRW-491

Still missing is that the vsix files we can't ref from MS should be built and published on https://download.jboss.org/jbosstools/vscode/3rdparty/ along with the others we have in https://download.jboss.org/jbosstools/vscode/stable/ that RH builds

@nickboldt nickboldt changed the title Setup a CI to build node-debug and node-debug2 vs code extensions Setup a CI to build node-debug2 vs code extensions Dec 10, 2019
@nickboldt nickboldt changed the title Setup a CI to build node-debug2 vs code extensions Setup a CI to build 3rd party vscode extensions Dec 10, 2019
@nickboldt
Copy link
Contributor

@nickboldt
Copy link
Contributor

https://github.com/eclipse/che-plugin-registry/pull/334/files merged to update Che 7.7 plugin reg to use dl.jb.o locations for newly built plugins. We can close this now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants