Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-544 CRW 2.1 plugins+images
  3. CRW-578

Build vsix files from 3rd party vendors and publish on dl.jb.o; get RH projects to co-locate vsix and sources

XMLWordPrintable

    • RHDP-232 - 1. Maintain existing portfolio commitments

      New plugins to build for CRW 2.1 include (versions are the latest as of today; if newer ones exist in Che plugin registry, use that instead):

      "joaompinto/vscode-asciidoctor/2.7.7

      "sonarsource/sonarlint-vscode/0.0.1

      "redhat/java11/0.50.0 (also used for gradle)

      "redhat/vscode-camelk/0.0.10

      "redhat/quarkus/1.2.0

      New plugins to get built by RH teams (or at least clean up their publishing process to get sources/vsix in the same place):

      "redhat/java11/0.50.0 (also used for gradle)

      "redhat/vscode-camelk/0.0.10

      "redhat/quarkus/1.2.0

      "redhat/rhamt/0.0.11

      Tracking status here:

      https://docs.google.com/spreadsheets/d/1TllnofYIlA7yTn7hIa8-LojGpHR1ACk1hVP-7fg_wsY/edit#gid=1935159288

      Steps:

      1a. 3rd party: build new vsix + sources tarball, push to dl.jb.o
      1b. RH team: improve release process so vsix and sources tarball are co-published on GH or dl.jb.o, whichever is easier for that team

      2. submit PR for update to CRW plugin reg, so we use the vsix files from the new hosted location
      3. submit PR for update to Che plugin reg, so we use the vsix files from the new hosted location

            nickboldt Nick Boldt
            nickboldt Nick Boldt
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: