Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-1223

Phase 1: Able to deploy Hub prod monthly

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • Phase 1: Able to deploy Hub prod monthly
    • False
    • False
    • Hide

      Complete child issues, and follow + document listed processes

      Show
      Complete child issues, and follow + document listed processes
    • To Do
    • 0% To Do, 0% In Progress, 100% Done

      Pre-requisites and process:

      • GH Actions run python and cypress functional tests on PRs
      • Deploy stage: manual, twice weekly, click to run regression tests, pre-reqs:
        • AAH-1219, AAH-1211
      • Jira fixVersion process: manual, twice weekly, look at commit history and add all merged issues since previous cloud release
      • Pre-prod deploy validation beyond regression tests, process:
        • Pause stage deploys and give QE 5 days (TBD) to give green light
          • Work through all items in “Ready for QA” for current cloud release
          • Manual test of syncing of the latest PAH z-stream versions against c.stage.rh.c
          • Manual ad-hoc testing of c.stage.rh.c UI
        • Schedule prod deploy 2 days after get green light
        • 48hr after prod deploy has no issues, resume twice weekly stage deploys
      • Post prod deploy, process:
        • Manual update to Jira release - rename cloud release from “Next Cloud Release” to “cloud-YYYY-MM-DD”
        • Manual update to GH tags: “cloud-YYYY-MM-DD” for galaxy_ng & ansible-hub-ui

              awcrosby5 Andrew Crosby (Inactive)
              awcrosby5 Andrew Crosby (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: