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

prevent inclusion of quay.io/devspaces images in stable branch builds of registries and operator-bundle

XMLWordPrintable

    • False
    • None
    • False

      As seen in CRW-3177, it's possible to:

      • accidentally include quay.io/devspaces/ images in the registries, and therefore in the CSV's relatedImages list (eg., quay.io/devspaces/udi-rhel8:3.1 instead of registry.redhat.io)
      • accidentally include the wrong version of images in the registries, and therefore in the CSV's relatedImages list (eg., quay.io/devspaces/code-rhel8:3.2 in the 3.1 registry)

      We should add some sort of gate/check that says:

      • if we have any refs to quay.io/devspaces/ images, in the list of related_images.txt or CSV for a stable-branch build (3.1, not 3.x), or
      • if we have any refs to devspaces images for a future/mismatched version, in the list of related_images.txt or CSV for a stable-branch build (eg., :3.2 in the 3.1 branch),
        ... then BREAK the all three of the registry (plugin, devvile) and bundle image builds

      That way forgotten changes or accidental cherrypicks-gone-wrong won't cause problems like we've seen in CRW-3177.

        1. image-2022-08-23-18-42-08-070.png
          image-2022-08-23-18-42-08-070.png
          36 kB
        2. image-2022-11-01-17-34-34-561.png
          image-2022-11-01-17-34-34-561.png
          89 kB

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

              Created:
              Updated:
              Resolved: