The model applied with the Evergreen distribution system is one similar to
"deploying" Software-as-a-Service, without having a centralized "production"
environment. When documentation refers to a "Deployment", that entails a new
"Upgrade" of Jenkins Evergreen being made available in the Evergreen hosted
service layer, and the backend orchestration necessary to ping connected
Instances to initiate their local upgrade process.
A Deployment is then considered successful when all connected Jenkins
Evergreen Instances are running that new version of Jenkins Evergreen.