-
Epic
-
Resolution: Done
-
Undefined
-
None
-
None
-
Containerized builds for long-lived deployments
-
False
-
-
False
-
In Progress
-
0% To Do, 0% In Progress, 100% Done
-
OCM Core Sprint 253, OCMUI Core Sprint 254, OCMUI Core Sprint 255, OCMUI Core Sprint 256, OCMUI Core Sprint 257, OCMUI Core Sprint 258
Follow the common convention for containerized builds, to implement the required pipeline parts to deploy the app to the staging and production environments (preview and stable).
Parts of this work have already been implemented for, or duplicated by, the PR pipeline (intended for short-lived deployments to ephemeral cluster. WIP), so a similar process should be followed here.
Generally this would consist of several steps, which should be repeated for each environment (staging, production/preview and production/stable, in this order):
- In uhc-portal, add a new build_deploy.sh script, with identical contents as pr_check.sh. This will build and push an image for the relevant environment.
- In app-interface, verify the above script is properly hooked and triggered via our (jenkins) job templates, or create new definitions to support it. This will pull the created image and deploy it onto console-dot.
See OCMUI-92, which depicts the recipe, and contains references to relevant documentation and guides.
- depends on
-
OCMUI-69 app fails to load when built as containerized
- Closed
-
OCMUI-1612 Add sass config to ui-dev permissions
- Closed
- relates to
-
OCMUI-92 Containerize OCM UI front-end for ephemeral enviornments
- To Do
- mentioned on