Do you Deploy to other Environments?

Last updated by Tiago Araújo [SSW] 6 months ago.See history

This rule has been archived
Archived Reason: Deprecated - Currently we deploy with PowerShell and Infrastructure-As-Code via platforms like GitHub and AzureDevOps.

Once you have configured “Build Once, Deploy Many” you can open the folder for any build on the build server and deploy any build, to any environment.

This means that if you deploy version 37, and then want to roll back to version 36 simply open the folder for 36 and re-run that batch file (assuming there has been no breaking DB schema changes).

TODO: AdamS – Write a rule on non-breaking Schema changes

deploy other environments
Figure: To deploy to staging and production, open the appropriate drops folder and execute the correct batch file from the drops folder

We open source. Powered by GitHub