Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-9160

Need a process for catching issues with upgrades between versions

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Obsolete
    • Icon: Normal Normal
    • None
    • None
    • Pipelines
    • 1
    • False
    • None
    • False
    • Testable
    • No
    • No
    • No
    • Pending
    • None
    • ML Ops Sprint 1.29

      Context:

      In the past we have encountered blockers after code-freeze where upgrading from a previous rhods version to latest resulted in breaking dspo/dsp deployments, resulting in alerts, etc. We want to be able to catch such issues before code freeze, which requires adopting version uprades as part of our development process in someway.

       

      Acceptance criteria:
      A proposal on how to perform regular upgrade testing as part of the dev process (does upgrade from old version -> new version result in failures/alerts/etc.?)

              Unassigned Unassigned
              humairkhan Humair Khan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: