• Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • True
    • Hide

      FedRAMP still relies on non-containerized builds.

      Show
      FedRAMP still relies on non-containerized builds.
    • False

      before cleanup, switch-off or remove repo' webhooks, as each phase (staging/production) gets done.

      the old pipelines has hooks named ocm-portal-deploy-*, and their corresponding jobs are defined in app-interface.

      these webhooks are auto-generated via the jenkins jobs' config. those jobs have to be deleted in order to completely remove the webhooks.

      constraints

      • we cannot detach candidate without affecting the release process, i.e. changing it to a 2-stage, so those should be done in accordance
      • we have to keep old Staging and Prod/Stable around (as well as push_to_insights.sh code etc.), for FedRAMP releases, until they migrate the UI to use containerized-builds (possibly at some point)

      implications

      detachment of any of these jobs would result in these consequences:

      1. uhc-portal's push_to_insights.sh will not get triggered in the corresponding mode (and branch)
      2. which will not build, package and push our code to the uhc-portal-frontend-deploy repo
      3. and not get picked-up by old deployment pipelines
      4. which now actually go nowhere, anyway (because the env', e.g. console.dev, is now re-routed to the new, containerized deploy' pipelines)

      it seems there's no real impact to source-code (aside from cleaning up redundancies, which is tracked separately).

      as for process, i can't spot any implications on staging/stable(+preview) or production/stable..
      but if we switch-off prod'/preview (candidate) with no backup env' (which would be the case after /preview has phased out & production have been fully containerized), we must change our promotion flow, to a 2-stage process; staging --> production.

      if push_to_insights.sh does not get triggered, FedRAMP will not get fresh deployments, as it still relies on the old build pipelines.

      action items / acceptance criteria

      • switch off staging: ocm-portal-deploy-staging)
      • switch off production/beta: ocm-portal-deploy-candidate
      • switch off production/stable: ocm-portal-deploy-stable

      (ATM we can't switch-off staging and prod'/stable, unless FedRAMP stops using them)

              emalka@redhat.com Eliran Malka
              emalka@redhat.com Eliran Malka
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: