Fixing Bugs and Preventing Regressions with More than One Test Environment
webdeveloperdiary.substack.com
Hi Friends When building software, it’s quite usual for a company to have more than one environment to deploy to. Depending on how many there are, managing these environments and their respective branches in source control can become tricky. In one of the more basic scenarios, we might have one internal staging environment for deploying a test build onto. Once QA have done their magic and given it the green light, that build could then be deployed to production for the next release. In this setup, there are two branches corresponding to each of the environments: staging, and production.
Fixing Bugs and Preventing Regressions with More than One Test Environment
Fixing Bugs and Preventing Regressions with…
Fixing Bugs and Preventing Regressions with More than One Test Environment
Hi Friends When building software, it’s quite usual for a company to have more than one environment to deploy to. Depending on how many there are, managing these environments and their respective branches in source control can become tricky. In one of the more basic scenarios, we might have one internal staging environment for deploying a test build onto. Once QA have done their magic and given it the green light, that build could then be deployed to production for the next release. In this setup, there are two branches corresponding to each of the environments: staging, and production.