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

Phase 2: Able to deploy Hub prod every 2wk

    • Icon: Epic Epic
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • QE
    • Phase 2: Able to deploy Hub prod every 2wk
    • 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:

      • Deploy stage backend automatically on commit to galaxy_ng
      • Deploy stage backend automatically on commit to automation-hub-deploy
        • Discuss: add full devshift pr-check from galaxy_ng into this repo? (if so add a Jira issue), or maybe have galaxy_ng devshift pr-check use master branch of automation-hub-deploy. Explore options to programmatically update deploy-clowder.yml
      • Deploy stage frontend automatically on commit to ansible-hub-ui
        • Confirm we want frontend/backend deployments to stage (and eventually prod) to be decoulped from one another, if so we need a devshift pr-check to run full stack in this repo using master on the backend repos
        • Explore options to automate frontend deploys
      • Pre-prod deploy validation beyond regression tests, process:
        • Pause stage deploys
        • QE does 1 day of remaining manual validation on stage, then gives green light
        • Schedule prod deploy 1 day after green light
        • 48hr after prod deploy has no issues, resume automatic stage deploys

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

                Created:
                Updated:
                Resolved: