I’m trying to understand how teams (or solo developers) actually kick off deployments. Not the runtime (K8s, VMs, ECS etc) ... but the hook/trigger/pipeline that rolls out code.
Synthesized Answer
Based on 1 community responses
Teams trigger deployments using various methods, including GitOps, where a push to a specific branch (e.g., 'main') triggers a deployment. Others use CI/CD pipelines with scripts running on CI servers, webhooks, or ChatOps commands. The choice of trigger mechanism depends on factors like team size, simplicity, and reliability needs. For instance, smaller teams might opt for simpler GitOps workflows, while larger teams may require more complex CI/CD pipelines with multiple approval gates.
Key Takeaways
GitOps with branch-based deployment triggers
CI/CD pipelines with scripts on CI servers
Webhooks or ChatOps commands for deployment triggers
I like to deploy automatically from pushes to dev, staging and main which are all gated by mandatory PR reviews, and any scripts run from Lambda which are gated by account access, so it's always a deliberate occurrence and only certain people can trigger it and nobody needs to be doing anything manually against the environments.