Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-4564

OSSM 3.0 Productization Pipeline

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Blocker Blocker
    • OSSM 3.0-TP1
    • None
    • Sail Operator
    • None
    • Productization Pipeline
    • False
    • None
    • False
    • Done
    • 0% To Do, 0% In Progress, 100% Done
    • Sprint 12, Sprint 13

      There is a need to plan and implement a productization pipeline that will provide the following workflow tasks:

      • Downstream builds via CPaaS
      • Automated deploy and test.
        • To reduce release-cycle time, it will be important not to over test nor add test duplicity of testing that will already have been done prior to a downstream build.
        • Re-use as much upstream testing (Istio integration tests, etc) as possible (see: https://issues.redhat.com/browse/OSSM-4504) and avoid duplicating upstream tests downstream.
        • Identify key downstream tests that cannot be validated upstream (ie platform specific - such as P/Z, upgrades, etc)
        • This was moved to https://issues.redhat.com/browse/OSSM-4807
      • Automated Errata workflow

      Objectives:

      • Release within 24 hours
      • Minimal (to no) downstream manual testing or manual errata workflow tasks. The desire is for entire release workflow to be automated.

      Service Mesh v3.0 - CI / CDWorkflow

              fbrychta@redhat.com Filip Brychta
              mmahoney@redhat.com Matthew Mahoney
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: