New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introducing a stage environment #653

Open

Makman2 opened this issue Mar 19, 2019 · 1 comment

Member

Makman2 commented Mar 19, 2019

Have corobo changes land in a staging instance before deploying to production (what keys will be different in staging? If none, this is useless. If some, the staging wont be testable unless labhub is connected to a different ‘dummy’ org, and then nobody will use it.)

Separated from #509

Makman2 mentioned this issue

corobo security hardening #509

Closed

8 tasks

gitmate-bot added the bug label

Makman2 removed the bug label

Member Author

Makman2 commented Mar 19, 2019

Currently I don't see major benefits in introducing a staging system compared to the effort to introduce one, because

someone has to conduct manual tests on it to make it actually useful. I rather prefer to do continuous deployments and fix things fast. Problems are then covered by automated tests instead of manual ones (leads to more reliable deployments).
necessity to manage infrastructural resources needed by the staging system (an org, gitter channels, secrets, ...)

The only benefit to me is

allow to quickly test new features by deploying to stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment