We want to define and document the process for manual deployment, not automate it (unless it's very easy).
The current docs on how to build the debian package are:
https://gerrit.wikimedia.org/r/plugins/gitiles/cloud/toolforge/toolforge-cli/+/refs/heads/main
The only docs I've found are:
https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Services#apt_repository
Though it does not say how to add a package, the standard way I think is:
- ssh to the tools-services* VM
- sudo -i
- aptly repo add <repo_name> <path_to_package>
- aptly publish --skip-signing update <repo_name>
Where the repo_name is one of:
- stretch-tools
- buster-tools
- stretch-toolsbeta
- buster-toolsbeta
This task is to verify the flow, and document it in the README file or similar.