Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
54
Description
Context:
It is possible to use Optimize in a docker. Right now, we test the docker build manually on the release tests (if we remember to do it). In the last alpha release, we forgot to check the docker build and a customer raised the issue SUPPORT-7157. To make sure that the docker release build works we should have a post-build step in the release pipeline to do some simple smoke testing.
AT:
- a new step is added to the release build pipeline that checks that Optimize docker image works.
- works == there is a smoke test that ensures that the image can be started
- it calls the /api/status endpoint and verifies that it's an OK response - to verify the backend is up and running
- it fetches the /index.html to verify the frontend is present