Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-2733

MCE 2.3 / ACM 2.8 Release Cutover

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Blocker Blocker
    • ACM 2.8.0, MCE 2.3.0
    • ACM 2.8.0, MCE 2.3.0
    • DevOps
    • None
    • MCE 2.3 / ACM 2.8 Release Cutover
    • False
    • None
    • False
    • Green
    • To Do
    • 14% To Do, 0% In Progress, 86% Done
    • ACM Sprint 26

      Summary

      As we pivot active development to MCE 2.3 / ACM 2.8, the time has come to cut-over active forward development to MCE 2.3 / ACM 2.8 release/backplane branches. This process starts with the generation of new backplane-pipeline and pipeline backplane/release branches for 2.3/2.8 followed by the creation of equivalent branches in the release repo. After this is complete, squads generate backplane-2.3 or release-2.8 branches in every repo targetting those releases and update their OSCI jobs to fast-forward and publish to 2.3/2.8. Finally, CICD validates that the upstream build is up-to-date and installable and bootstraps a downstream build and delivery pipeline for MCE 2.3 / ACM 2.8.

      Progress

      • COMPLETE - backplane-pipeline and pipeline 2.3/2.8 branches created
      • COMPLETE - release 2.3/2.8 branches created
      • COMPLETE - MCE 2.3 / ACM 2.8 upstream builds validated installable
      • COMPLETE - MCE 2.3 / ACM 2.8 component cut-over
      • COMPLETE - MCE 2.3 / ACM 2.8 downstream builds online

      Future Work

      ACM-1715 captures the work necessary to fully automate this process

            Gurney.Buchanan@ibm.com Gurney Buchanan
            Gurney.Buchanan@ibm.com Gurney Buchanan
            Christopher Bynum Christopher Bynum
            Gurney Buchanan Gurney Buchanan
            Brian Smith, Emily Macdonald, Kyl Bempah
            Joe Gdaniec Joe Gdaniec (Inactive)
            ACM DevOps
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: