The infra.git repository contains services which tend to fall into three different categories: single-homed cron services, multi-homed cron services, and appengine apps. The deployment mechanisms for each of these types of services are outlined here.
Many services are deployed as Buildbot jobs on the Infra Cron Buildbot waterfall. These services all have the same basic form:
This strategy has a few ramifications for deployment:
In order to combat tip-of-tree breakages, these services do not run from ToT of the master branch. Instead, they operate in detached-HEAD mode, checking out the remote ref origin/deployed before each run.
In order to update the code being run by gsubtreed or other similar services you have to push a new value to the origin/deployed ref:
git push origin master:deployed
You can also push specific hashes:
git push origin deadb33fb4adecafdeadb33fb4ddecafdeadb33f:deployed
And for rollbacks, just make sure you pass the
--force flag (this should be rare):
git push -f origin deadb33fb4adecafdeadb33fb4ddecafdeadb33f:deployed
Some of our services (in particular monitoring services such as sysmon and mastermon) are deployed across a wide variety of hosts. These services are not deployed via source checkouts. Instead, they are packaged by CIPD (the Chrome Infra Package Deployer). The CIPD packages are built for every green revision by the infra-packager-* builders in the luci.infra-internal.prod bucket/pool. Selected versions of these packages (not the packages themselves) are deployed to specific hosts by Puppet. For instructions on how to update the version of the CIPD package for these services, see the documentation in the Puppet repository.
There is no single procedure how to deploy appengine apps. Normally, each app author deploys his/her app manually, using gae.py tool.