Uploaded image for project: 'Helm'
  1. Helm
  2. HELM-189

Enable release pipeline in CPaaS

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • Helm, QE
    • AppSvc Sprint 202, AppSvc Sprint 203, AppSvc Sprint 204, AppSvc Sprint 220, AppSvc Sprint 221, AppSvc Sprint 222

      • The release pipeline in CPaaS is supposed to be triggered by a UMB message from the test job with results. 
      • Enable stages needed in a release pipeline
        • Adding errata for release pipeline
        • Attaching builds to the errata
        • requesting QE and Docs approval

      Background:

      Currently the release pipeline has not enabled any stages.

      release config here: https://gitlab.cee.redhat.com/cpaas-products/ocp-tools-helm/-/blob/v3.7/release.yml#L36

       

      Approach:

      Need to trigger the UMB message after the helm acceptance test job finsihes.

      Enable Release Pipeline stages that will create the errata advisory, attach build and move errata to qe state.

      As described here https://docs.google.com/document/d/1ky6TxwcGYLs2XY6abjAVKbDCAnaDAyyPCeeF1VwLKh0

       

      Acceptance Criteria:

      After completion of the release pipeline, errata should be created with expected content.

      Build attached is correct one.

      Errata is in QE state after the release pipeline finsihes.

            susdas@redhat.com Sushanta Das
            pjagrut Pratik Jagrut (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: