Uploaded image for project: 'Red Hat OpenBridge'
  1. Red Hat OpenBridge
  2. MGDOBR-414 Investigate and define initial tasks to start the onboarding process for CPaaS
  3. MGDOBR-625

Configure release pipeline

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • False
    • None
    • False
    • OpenBridge Sprint 216, MAS CCS - Sprint 217, MGDOBR - Sprint 218, MGDOBR - Sprint 219, MGDOBR - Sprint 220, MGDOBR - Sprint 221, MGDOBR - Sprint 222, MGDOBR - Sprint 223, MGDOBR - Sprint 224, MGDOBR - Sprint 225, MGDOBR - Sprint 227, MGDOBR - Sprint 228, MGDOBR - Sprint 229, MGDOBR - Sprint 230

      Issue Description: 

      The role of the release pipeline is to deliver the newly built artifacts to managed-tenants. This pipeline will, once configured:

      1. Mirror the built images as well as the relatedImages to quay.io
      2. Generate an index that serves the mirrored bundle
      3. Submit an MR to managed-tenants that updates the add-on to use the newly generated index

       

      Configure the release pipeline to deliver as a Managed Service.

      • product-configs configuration: Set the managed-service field to true
      • release.yaml: Set name as “ms-release” and the deliver-content field to true

       

      Once the Jenkins instance is updated, the ms-release job is generated. The release pipeline will, be default, run once the tests pass on the bundle build job

      Acceptance Criteria:

              Unassigned Unassigned
              vajain Vaibhav Jain
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: