Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2412

Migrate devfiles v1 to v2 (part 1)

    XMLWordPrintable

Details

    • False
    • False

    Description

      The idea is to migrate existing devfiles v1 to v2.

      NOTE: Since there is insufficient time remaining in the 2.14 cycle, this issue has been broken into two parts. It starts here w/ fixversion 2.14, and continues in CRW-2539 for 2.15.

      More information about devfiles version 2 can be found in upstream issue https://github.com/eclipse/che/issues/19341

      CRW already has one implemented devfile v2 for quarkus sample https://github.com/crw-samples/quarkus-quickstarts/blob/devfilev2/devfile.yaml and the link to this devfile was added in the meta.yaml https://github.com/redhat-developer/codeready-workspaces/blob/crw-2-rhel-8/dependencies/che-devfile-registry/devfiles/03_java11-maven-quarkus/meta.yaml#L7

      Current list of samples (devfile v1):

      Attachments

        Issue Links

          blocks

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. CRW-2474 CRW 2.15 overall epic

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          QE Task - QE Task CRW-2540 Update devfile tests to verify v2 versions in DW enabled CRW (part 1)

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          QE Task - QE Task CRW-2541 Update devfile tests to verify v2 versions in DW enabled CRW (part 2)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          causes

          Task - Represents a small unit of work that is not end-user facing. CRW-2578 devfile v2 caching for devworkspace airgap support needs to be arch-aware and swap jdk images for j9 on Power/Z

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is cloned by

          Task - Represents a small unit of work that is not end-user facing. CRW-2539 Migrate devfiles v1 to v2 (part 2)

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          is related to

          Task - Represents a small unit of work that is not end-user facing. CRW-2500 [airgap] Pre-build DevWorkspace templates for devfile v2 of devfile registry

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. CRW-2253 DevWorkspace fails to start when use factory link from upstream java-spring sample

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          links to

          Web Link Certificate issue when downloading zip files from the registry

          Activity

            People

              vsvydenk Valerii Svydenko
              vsvydenk Valerii Svydenko
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: