Allow QA to test the final production build

unfoldingWord / tc-create-app

translationCore Create

https://create.translationcore.com/

MIT License

0 stars 5 forks source link

Allow QA to test the final production build #635

Closed birchamp closed 2 years ago

birchamp commented 3 years ago

Currently the workflow requires a new build for production. This means that the production build is not what QA tested. We need to find a way to either use the commit hash as the build number or restrict access to the production build until it's ready to be released.

birchamp commented 3 years ago

@klappy @ancientTexts-net Can this be handled in Netlify? A production build that uses the production server but not fully released so QA can look at it first.

ancientTexts-net commented 3 years ago

meeting witih @richmahn & Jaap-Jan

discussed current DCS/gitea environments & ways to provide what Kos/Elsy need

Spreadsheet: https://docs.google.com/spreadsheets/d/1nY023IJa1sZZWulp5EO4ed8iY6f7aIQSb8Q_vzVgg4s/edit?ts=60af92d1#gid=0

Notes

ancientTexts-net commented 3 years ago

@elsylambert @cckozie

https://stage--tc-create-app.netlify.app/

current "pre-production" build (release build codebase -- not RC)
uses PROD data

elsylambert commented 3 years ago

Verified https://stage--tc-create-app.netlify.app/

uses Prod (git.door43.org)- works as expected.
- Build version is incremented from develop which is a known problem currently.
- Live site is unaffected by this change-as expected.

Looks good at this point as it serves the purpose for QA to test pre-release build.

cckozie commented 3 years ago

v1.2.1 build 54-23bc2b8 I concur with Elsy's comment above.

ancientTexts-net commented 3 years ago

♥ thanks Elsy & Kos

elsylambert commented 3 years ago

@ancientTexts-net reported issues when merging PR from Staging to Production. This issue is partiality solved in terms of allowing QA to test pre-production and making the final production release.

ancientTexts-net commented 3 years ago

here's the diff of the netlify builds nothing major in the packages section

we could compare the ZIPS if we want

ancientTexts-net commented 3 years ago

on standup, agreed to spend [4] hours diagnosing

what was root cause (compare ZIPS)
is there an easy way to deploy ZIPS to netlify without rebuilding ?

birchamp commented 3 years ago

@ancientTexts-net try a commandline diff tool

elsylambert commented 2 years ago

This works fine. QA is able to test with Production data on Staging server.