Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-3564

1 click releases (end to end automation) ⚡

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • None
    • p12n
    • 1 click releases (end to end automation) ⚡
    • False
    • None
    • False
    • To Do
    • 100% To Do, 0% In Progress, 0% Done

      this epic tracks automation needed to eliminate manual intervention while doing releases

      🔥 after code freeze (and 5.0.5 🤷)

      the following is true for release branches including 5.0.5

       

      when code freeze is done, the following happens automatically:

      • a release branch is cut in gitlab/p12n repo from the 5.0.5 branch
      • maxOpenShiftVersion, etc should be configured
      • HB and cpaas configs are created
      • errata is created
      • we also need to figure out git based release notes where they are updated each time the release notes field is updated
      • whenever the release notes are updated in an issue in jira, the update is posted to a git repo / dashboard
      • write a mechanism to automatically collate upstream release notes as well in a release based on upstream components’ version bumps

              Unassigned Unassigned
              concaf Shubham Minglani
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: