How many human or manual interactions are there between commit and deploy?
TL;DRGetting a build takes two human steps (commit and kicking the build), with possibly one more for internal staging, while large environments need a human decision but provisioning and configuration are automated.
To get a build, there's only two. It'd be the developer making the commit and then the developer kicking the build. Depending on what environment you're wanting to deploy to, it could be potentially one more human interaction, which uses the same interface we kick our builds through to deploy to our internal staging environments. I think Ahmed could address outside of that for me.
If it's a larger environment, it goes through people deciding that this is the build we want to go with, and then from then the humans just make the decisions, what we were talking about earlier. Everything is driven by version control, everything is driven by Git, but there is a human saying yes. And we did not abstract that into a GUI yet, we didn't see the need for that. We call ourselves DevOps. I know this is some kind of heated topic for a lot of people. DevOps is a philosophy, not a title, but that's what the market goes for. But we try to really hold the values of DevOps close to us. We share the ownership of that product. This gaming experience is ours. I can spend more than 50% of my time investigating an issue about how a player isn't able to connect to something, because I have the access to all these tools and I can try to go and investigate it. To go back, when it comes to deployment to a larger environment, that's usually where human decisions are being implemented, but all the actual work of provisioning, configuring, securing is automated. It would take days, it would take weeks to deploy the whole environment manually with how it spreads around the world.