From 72d6d937c48fdb5326d10a7b2b9ea603483699fd Mon Sep 17 00:00:00 2001 From: Jay Moran Date: Mon, 18 Sep 2023 13:33:11 -0700 Subject: [PATCH] Update release procedure instructions --- docs/guides/developerGuide.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/guides/developerGuide.md b/docs/guides/developerGuide.md index bbc57a0f2..ea6ff2ed4 100644 --- a/docs/guides/developerGuide.md +++ b/docs/guides/developerGuide.md @@ -366,20 +366,21 @@ branch and push the changes to github. build the production images and generate the user production .zip by running `bash release/generate_production_release.sh`. This will: - - Create local lab, machine, and dbmongo production docker images with the + - Create lab, machine, and dbmongo production docker images with the tag defined in the .env file - Create the production .zip named `target/production/Aliro-${VERSION}.zip` + - Build multi-architecture (amd64, arm64) docker images using `buildx bake` and push the images to docker hub. ```bash git checkout production bash release/generate_production_release.sh ``` -4. **Push docker images to DockerHub and tag the production git branch by +4. **Check that the docker images were pushed to DockerHub and tag the production git branch by running `deploy_production_release.sh`.** While in the produciton branch, run `bash release/deploy_production_release.sh`. This will: - - Push the production lab, machine and dbmongo production docker images to dockerHub + - Check that the production lab, machine and dbmongo production docker images exist in dockerHub - Tag the production git branch with the version defined in `.env` ```bash