3 ms·
My company build something pretty identical to this a few years ago. It's INVALUABLE if you have a QA team or non-tech people who need to test things on differe
by Jemaclus 11y ago
My company build something pretty identical to this a few years ago. It's INVALUABLE if you have a QA team or non-tech people who need to test things on different branches. Our workflow basically went like this:
1. Dev pushes branch to repo
2. Dev assigns ticket to QA
3. QA builds a sandbox server
4. QA tests everything under the sun
5. Any bugs are pushed to repo and auto-pushed to sandbox server
6. After QA gives green light, sandbox server is taken down.
Average uptime for a sandbox server was a few hours, and we caught a bazillion bugs this way. I'm no longer with that company, so it's really exciting that someone else has built something like this off-the-shelf so that I can continue with that workflow at future jobs. :)
- ykumar6 11y agoFounder here. Check us out for your future jobs. Maintaining sandbox infrastructure is a pain. One of our key lessons is being able to dispose and rebuild your infrastructure on a daily or weekly basis so leaks don't destroy your environment. We recycle customer environments in Runnable, on a regular basis and its completely transparent to users