Uploaded image for project: 'OCMUI - OpenShift Cluster Manager UI'
  1. OCMUI - OpenShift Cluster Manager UI
  2. OCMUI-3136 deploy to production from master
  3. OCMUI-3174

deploy to production from master - with manual intervention

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • OCMUI Core Sprint 268, OCMUI Core Sprint 269, OCMUI Core Sprint 270

      • draft new release https://github.com/RedHatInsights/uhc-portal/releases/new choosing (new tag like feb-28-2025 target master previous tag: whateverthepreviousdate -> release notes will be generated
      • workflow will wait for the https://console.redhat.com/apps/openshift/app.info.json to contain the new commit hash to execute ./run/label-release-jira.mjs --jira-token <auth-token>
      • workflow will post a message on #ocm-osd-ui channel from slack
      • documentation, trying to cover all the possible exceptions for the release manager to be able to react in case of procedure failure

              Unassigned Unassigned
              emingora Enrique Mingorance Cano
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: