Following devrel issue 135, this issue has Automation leveraging the existing CICD code to deploy base branch builds to some staging environment so the Developer Relations team can test their changes in the cloud before deploying them to production.
See Also
- devrel issue 80 - Standup DevHub Infrastructure
- devrel issue 96 - DNS Mapping for learn.eosnetwork.com
- devrel issue 134 - Update DevHub Site
- devrel issue 135 - DevHub Frontend CICD
- devrel issue 137 - Encrypt DevHub Backend
- devhub issue 12 - Put AWS Resources into Terraform with a CICD Deployment
- devhub issue 13 - Document CICD System
- devhub issue 14 - Staging Environment
- devhub issue 15 - Backend CICD
- devhub issue 16 - Structures CICD
- devhub issue 17 - Add a JavaScript/TypeScript Linter to the DevHub Projects
- devhub issue 18 - Add BASH Linters for CICD Code
- devhub issue 19 - Include Test Suite in CICD
Following devrel issue 135, this issue has Automation leveraging the existing CICD code to deploy base branch builds to some staging environment so the Developer Relations team can test their changes in the cloud before deploying them to production.
See Also