Closed birchamp closed 2 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.
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
@elsylambert @cckozie
https://stage--tc-create-app.netlify.app/
Verified https://stage--tc-create-app.netlify.app/
Looks good at this point as it serves the purpose for QA to test pre-release build.
v1.2.1 build 54-23bc2b8 I concur with Elsy's comment above.
♥ thanks Elsy & Kos
@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.
here's the diff of the netlify builds nothing major in the packages section
we could compare the ZIPS if we want
on standup, agreed to spend [4] hours diagnosing
@ancientTexts-net try a commandline diff tool
This works fine. QA is able to test with Production data on Staging server.
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.