Draft of the current node.js services deployment process: https://wikitech.wikimedia.org/wiki/User:Mobrovac/Service_Deployment

@fgiunchedi: if you have anything to add, please add your thoughts on requirements for sentry deployments

sure, context is https://gerrit.wikimedia.org/r/#/c/201006/ where a python virtualenv is shipped in git, also note that sentry isn't currently deployed but it'll likely be in the future.

One big problem I see ATM is that python virtualenv --relocatable doesn't really work in practice (https://virtualenv.pypa.io/en/latest/userguide.html#making-environments-relocatable) so the path has to be the same in both build host and runtime host

general points I've identified while looking at the code review, mostly on the 'deploy working code onto machines' side of things, rather than deployment policies/mechanics themselves

• lots of binary files in git which likely change (e.g. .pyc), big size too
• a 'build' must be easily reproducible, even if it lives in git (e.g. for security updates)

Here's my attempt at diagramming the process as a sequence diagram.

see P709 for the source code